MQSeries.net :: View topic

p.cradwick · Posted: Tue Mar 28, 2006 6:01 am Post subject:

We are running V6 broker on Linux and having problems with the aggregation reply node. There are 2 flows, fan_out and fan_in. The latter reads a response Q from external app. These flows worked fine on Windows with expected behaviour. When they were ported to Linux, through an oversight, there were a couple of test messages from the external app. on the response queue, so the fan_in processed these as replies and generated 'unknown' responses. Unfortuneately, it continued to do this at the rate of one unknown response per sec although there were no messages on the queue. We thought we had stopped the flow and went home only to find syslog filled up over night. Not the recommended way to stop flows!

Any one seen this odd behaviour?

Incidently in accordance with the v6 docs, we don't use a control message between the control and reply nodes. Do other people do this i.e. drop the control message?

regards
Peter