Posted: Fri May 10, 2013 3:12 am Post subject: SYSTEM.BROKER.TIMEOUT.QUEUE
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
I deployed my timeout flow and i see a msg gets created in the system timeout queue whenever a timeout message reaches the timout control node and it sits there until the timeout condition is met and it is sent downstream to the timeout notification node.
But if i delete the flow from the EG before the timeout condition is met this msg just stays on the system queue indefinitely. I am having to delete the msg manually.
Now if i redeploy the flow this msg is gone and a new timeout msg sits on the queue.
If i redeploy on top of existing flow the message gets wiped out again and new timeout message goes again on the queue and waits there for timeout condition to be met.
Would be nice to know how this timeout queue works.
the way i see it the only time an orphaned message will be in the timeout queue is if a flow is deleted from the EG and never deployed again on the same EG.
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