|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
What happens when the message read by MQGet node errors out |
« View previous topic :: View next topic » |
Author |
Message
|
Senthamizh |
Posted: Wed Sep 08, 2010 12:27 pm Post subject: What happens when the message read by MQGet node errors out |
|
|
Apprentice
Joined: 21 Dec 2009 Posts: 47
|
Hi,
I am new to MQGet node and just need a clarification on the functionality of the MQGet node, before desigining a flow.
I have a flow like this MQInput -> Compute1 -> MQGet -> Compute2 -> MQOutput
A message on the MQInput triggers the flow and we poll on a queue specified in MQGet for some time and then we build a new output with the message read(not browse) from MQGet node.
I would like to know, what will happen to the message if it fails in the Compute2, after the MQGet reads the message with no error code.
1) Will it roll back to the MQInput node?
2) Will it roll back to the MQGet Node?
3) If it rolls back to MQGet Node, will it go to the specified backout queue, if the BOQTHRESH is set correctly and we increase the BackOut count? or will it stay in he MQGet Node queue even if we set a backout with reqd parameters?
I tried doing a simple flow on this, and for me the message stayed in the MQGet Node queue, whenever the message failed in the Compute2. I increased the MQMD BackoutCount value when the messaged failed so that it could go to the backout queue specified for MQGet , but it did not, it stayed in the same queue mentioned in MQGet node.
I would like to know if this is the functionality of MQGet or i am missing something, Could somebody help me out. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Sep 08, 2010 12:30 pm Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
Vitor |
Posted: Wed Sep 08, 2010 12:51 pm Post subject: Re: What happens when the message read by MQGet node errors |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Senthamizh wrote: |
I would like to know, what will happen to the message if it fails in the Compute2, after the MQGet reads the message with no error code. |
Do you mean the message read by the MQGet node or the message read by the MQInput node?
Senthamizh wrote: |
1) Will it roll back to the MQInput node? |
Whatever your answer to my above question, the answer is "it depends on what you've configured the flow to do".
Senthamizh wrote: |
2) Will it roll back to the MQGet Node? |
See above
Senthamizh wrote: |
3) If it rolls back to MQGet Node, will it go to the specified backout queue, if the BOQTHRESH is set correctly and we increase the BackOut count? or will it stay in he MQGet Node queue even if we set a backout with reqd parameters? |
That doesn't make sense the way you've written it. But backout threshold is honoured.
Senthamizh wrote: |
I increased the MQMD BackoutCount value when the messaged failed so that it could go to the backout queue specified for MQGet , but it did not, it stayed in the same queue mentioned in MQGet node. |
Read that back, realise what you've done wrong and be very ashamed. Even if you're new to the MQGet node you should realise why that didn't work the way you wanted.
Senthamizh wrote: |
I would like to know if this is the functionality of MQGet or i am missing something |
You seem to be missing some fairly obvious facts about WMQ & WMB.  _________________ 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
|
|
|
|