What exactly kiran meant is a flow that stops working suddenly.
We have a flow that works for a while and suddenly stops working. Once I restart the execution Group the flow starts working fine. Every now and then I should see if the messages are being processed or not. From this I came to a Conclusion that the Flow gets hanged.We do have the catch terminal connected to our Generic Error handler process that will log the error and will shoot us an email
Is there a command or a way to see if the flow is active.
What exactly kiran meant is a flow that stops working suddenly.
We have a flow that works for a while and suddenly stops working. Once I restart the execution Group the flow starts working fine. Every now and then I should see if the messages are being processed or not. From this I came to a Conclusion that the Flow gets hanged.We do have the catch terminal connected to our Generic Error handler process that will log the error and will shoot us an email
Is there a command or a way to see if the flow is active.
Broker 7.0.0.5
OS : AIX
You may not see anything on the error handling. If the specific data in a message causes the flow to go into an endless loop, it will look as if the flow is hung... The only way you can analyze such a situation is by asking for a debug trace...
Have fun _________________ MQ & Broker admin
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
reddy2078 wrote:
We have a flow that works for a while and suddenly stops working. Once I restart the execution Group the flow starts working fine.
Check the message that are processed by the flow and check for the difference in them. Maybe your flow is going on a endless loop for one of the test case. Try to get that message and see what's wrong in your flow.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum