| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transaction mode in MQInput |
« View previous topic :: View next topic » |
| Author |
Message
|
| pvemuri |
 Posted: Wed Jan 05, 2005 2:07 pm Post subject: Transaction mode in MQInput |
 |
|
Voyager
Joined: 05 Jan 2004
Posts: 83
Location: CA, USA
|
Hello All,
I will explain my flow :
Input Q -> ComputeNode -> OutputQ1 -> CustomNode->OutputQ2
1. Compute Node adds MQMD details. (reply to Q etc)
2. OutputQ 1 is the request queue for a JTEXT adapter
3. CustomNode waits for a specified amount of time (can be set in properties) for the adapter to give the response back to its response queue. if it does not respond back in ## seconds then it will throw an exception. else the CustomNode picks it from the response queue and sends it to outputQ2
The reason behind implementing the CustomNode is due to some business requirement.
The issue here is :
1. If the Transaction mode property in MQInput node is "YES" then, the flow does not work. Probably because the message is in the request queue but is not available for JTEXT to process.
2. If the Transaction mode property in MQInput node is "Aoutomatic" then it works pretty fine.
I think if the Transaction mode is "YES" then due to the waiting / holding of the processing in CustomNode is not allowing the Message to be readable to JTEXT adapter.
Whats the difference between the modes Yes and commit. |
|
| Back to top |
|
 |
| javaforvivek |
| Posted: Thu Jan 06, 2005 4:32 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
The WBIMB Help gave me this:
| Quote: |
Configuring for coordinated transactions
When you include an MQInput node in a message flow, the value that you set for Transaction Mode defines whether messages are received under syncpoint:
If you set it to Yes (the default), the message is received under syncpoint (that is, within a WebSphere MQ unit of work). Any messages subsequently sent by an output node in the same instance of the message flow are put under syncpoint, unless the output node has explicitly overridden this.
If you set it to Automatic, the message is received under syncpoint if the incoming message is marked persistent. Otherwise, it is not. Any message subsequently sent by an output node is put under syncpoint, as determined by the incoming persistence property, unless the output node has explicitly overridden this.
If you set it to No, the message is not received under syncpoint. Any messages subsequently sent by an output node in the flow are not put under syncpoint, unless an individual output node has specified that the message must be put under syncpoint.
(The MQOutput node is the only output node that you can configure to override this option.)
|
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 06, 2005 5:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So, to clarify a little more what's happening with your flow...
If you set the transaction mode to YES, or to Automatic and your message is persistant, then the first Output node will not commit the putuntil the entire message flow has completed.
UNLESS you instruct the output node to change IT'S TransactionMode, to "No".
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
