MQSeries.net :: View topic - Filter Node stops routing messages until flow redeployed

jrsetters

I ran into this with a test flow and am trying to determine how I need to address it before production. I have a very simple Filter Node with a True/False condition evaluating a field in my message. If the TRUE condition is met, I move the message to three destination topics. If the FALSE condition is met, I move it to another.

The flow worked as expected for several weeks of testing before my users of one of the external systems began to complain that they did not see messages. I checked the inbound message contents and determined that they should have gone to the outbound system in question. I placed the flow into a Debug state and re-sent the messages. I watched it step through the eSQL in the Filter Node and distribute to two of the three destinations from the TRUE out node, but never the third. I deleted the connection between the TRUE node and the third topic and re created it. When I redeployed it worked again without issue.

I am not certain how to troubleshoot this any further since I did not have any active traces. But this is the sort of issue that would be frightening in production.

Has anyone experienced this before?

I am running 7.0.0.2 of the Toolkit and MQSI.