We have a requirement of introducing a Retry mechanism for one of the interface. The operation to be performed in the message flow looks like below
1. Read the message from the Input Queue
2. Create the SOAP Message to call WebService
3. Call the WebService and check the result
3.a IF WebService is down then go to Retry logic and retry to connect to the same Webservice 5 times after 10 Minutes
3.b IF Webservice is up and valid response is received then no need to take any action
Retry Logic
1. Take the original message from the Environment tree and create WebService message again
2. Check how many times the retry taken place, if it is less than 5 times then execute below step 3. Or else execute step4 below
3. Execute the step 3 above
4. Send the message to error queue
I have used Timer nodes to implement the retry mechanism. Due to some issue my flow went to Infinte looping and I have remvoed the flow from the Execution group restarted the broke.
Now when I deploy the flow once again after correcting the infinite loop issue its deployed successfully. However the previous instance of the flow getting poped up (The flow which was removed from EG).
I am suspecting this is because the unique ID used in the Timer nodes. Because if I change this unique ID with a new values it works fine.
Do any one know how to resolve above issue is I want to use the Same Unique ID.
When ever you use Timeout Notification nodes, the notification that need to be sent is persisted in queue SYSTEM.BROKER.TIMEOUT.QUEUE,
Remove or purge the above queue for the message stored from previous timeoutnotification entry OR send a CANCEL message for the previous notification message.
Hope this helps.
-peace _________________ IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
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