|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error Handling for MQ/MB |
« View previous topic :: View next topic » |
Author |
Message
|
jnoubi |
Posted: Fri Nov 02, 2007 6:30 am Post subject: Error Handling for MQ/MB |
|
|
Novice
Joined: 26 Sep 2006 Posts: 24
|
I am working on an error handling strategy for our environment which uses MQ 6.0 for transport and MB 6.0 for routing and transformation.
One of the strategies is to roll back messages into the source system in case the link with the target system is down.
So basically, in case the link between the MB and the target system is down (for any reason such as channel down, network issues,..), my strategy is to roll back any messages to the source system's queue (no DLQ is specified for the queue manager of the message broker and retry count is set to 5 for example). This works well because I am ensuring that incoming messages will stay in sequence and the source system will be forced to stop sending once their queue is full.
However, the problem that I am facing is how to restart the process of MB picking up the messages from the incoming queue once the link to the target system is restored?
So basically, the recovery strategy is not clear. If I manually remove the first message from the incoming queue (for ex using rfhutil), the flow is restarted. However, because one of my requirements is not to lose any message and not to lose the order of the messages, I can't manually remove messages.
Any suggestions to restart the flow without any loss of messages or order? |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Nov 02, 2007 7:03 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
|
Back to top |
|
 |
jnoubi |
Posted: Fri Nov 02, 2007 7:36 am Post subject: RE: |
|
|
Novice
Joined: 26 Sep 2006 Posts: 24
|
Yes, but one the repliers suggested I moved it to this forum. |
|
Back to top |
|
 |
rajmq |
Posted: Fri Nov 02, 2007 8:33 am Post subject: |
|
|
 Partisan
Joined: 29 Sep 2002 Posts: 331 Location: USA
|
Without manual intervention i don't think you can satisfy the requirement because you made a design like that,
We can do other way...
Option 1:
If you use Point to Point link between broker & target application then store the message in the xmitq queue.
Option 2:
Using error handler, send the input message to failure queue later you can reporcess the same also if required you can disable the flow queue for not processing other messages.
If mutiple applications are using the same flow again it is a problem so i would suggest to go option1. _________________ IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified System Administrator - WebSphere Business Integration Message Broker V6.0 |
|
Back to top |
|
 |
kirani |
Posted: Fri Nov 02, 2007 2:45 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
How would you know if the link to the target system is down? Are you planning to code this using a message flow? I agree with the post above that you let your messages build up in the XMIT queue is the link goes down. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|