Posted: Fri Jan 23, 2015 6:43 am Post subject: Problem with Timer nodes in IIB9
Acolyte
Joined: 20 Jul 2007 Posts: 72
Hello,
Iam using IIB9 and making use of timer nodes for achieving RETRY mechanism. But Iam stuck up with a wiered issue.
I have Timeout control and Timeout notification nodes working together to create timeout message and trigger messages every 30 seconds in case of a retry. If there is no need of retry, Iam cancelling the timer so that it does not generate any new messages. This works as expected when I test it with a message sent from rfhutil. But the problem comes up once I send a message from .NET application or a mainframe application.
And the problem is that it throws a "Timeout Set Identifier not in store" exception when Iam trying to cancel the timer.
My question is "Is this a known issue? " or some kind of bug in the product? Please let me know your thoughts.
Joined: 08 Aug 2011 Posts: 134 Location: Trivandrum
You may need to cross check:
The message header difference when sending from .net or other applications and when sending from RFHUtil.
Trace the timeout control message you are building to SET the TIMER (you can see this control messages in SYSTEM.BROKER.TIMEOUT.QUEUE queue by default).
Similarly trace the timeout control message you are building to CANCEL the TIMER (same unique identifier you have SET)
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