|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Transaction Mode in MQINPUT node |
« View previous topic :: View next topic » |
Author |
Message
|
asudhakar |
Posted: Tue Mar 18, 2008 8:29 pm Post subject: Transaction Mode in MQINPUT node |
|
|
 Centurion
Joined: 12 May 2007 Posts: 116 Location: Bangalore
|
Hi 2 all.
I have a simple message flow :
MQINPUT -> Compute -> MQOUTPUT
Transaction mode is yes in MQINPUT node.
i did nt define output queue in MQOUTPUT node.
then message will goes to DLQ.
But : I define No for Transaction mode in MQINPUT node.
i did nt define output queue in MQOUTPUT node.
Then message did not goes to DLQ.
even message was not in MQINPUT node.
I lost my message.
how can i save my message.
Can any one help me. _________________ WebSphere MQ, MB Support and Admin |
|
Back to top |
|
 |
gregop |
Posted: Wed Mar 19, 2008 12:16 am Post subject: |
|
|
Voyager
Joined: 24 Nov 2006 Posts: 81
|
You could wire the catch node of the MQ Input node and process the failed message from there. Though you'll still lose the message if something else fails.
If you need to save failed messages then its best to use Transaction = YES or AUTOMATIC with a persistent message.
See documentation on how to handle errors. |
|
Back to top |
|
 |
asudhakar |
Posted: Wed Mar 19, 2008 2:46 am Post subject: |
|
|
 Centurion
Joined: 12 May 2007 Posts: 116 Location: Bangalore
|
gregop wrote: |
You could wire the catch node of the MQ Input node and process the failed message from there. Though you'll still lose the message if something else fails.
If you need to save failed messages then its best to use Transaction = YES or AUTOMATIC with a persistent message.
See documentation on how to handle errors. |
Hi thank u.
But, can u tel me. if we give transaction mode is no.
Then what happened. And how its useful. _________________ WebSphere MQ, MB Support and Admin |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 19, 2008 2:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
asudhakar wrote: |
But, can u tel me. if we give transaction mode is no.
Then what happened. And how its useful. |
If the transaction mode is no, then the message is consumed because there's no transaction and no rollback.
On an Input node, it's seldom useful but is provided as an option for those cases where it is. It's the same story as through the whole of WMQ - if you can't stand the loss of a message, code to prevent the loss of a message. If you can stand the loss, then don't bother.
It's for this reason message persistence (for example) is a choice and all message are not forced to be persistent. Some messages can legitimately be lost. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|