| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transaction mode in MQInput node |
« View previous topic :: View next topic » |
| Author |
Message
|
| saturn_cemk |
 Posted: Tue Nov 07, 2006 7:21 am Post subject: Transaction mode in MQInput node |
 |
|
Novice
Joined: 10 Jul 2006
Posts: 16
|
Hi,
Environment: Windows XP SP2, WBIMB 6.0 and MQSeries 6.0
I have a message flow which looks like following:
MQInput ---> Compute ---> MQOutput
The queue used by the MQInput node has the Persistence property set to 'Persistent'.
The Transaction mode property in the MQInput node is set to 'Automatic'.
The Transaction mode and the Persistence mode properties in the MQOutput node are set to 'Automatic'.
The compute creates 3 messages from the input message and PROPAGATEs them to the output. But while creating the 3rd message an exception is thrown.
What should I get in the output in this condition ?
A. No messages
B. Two messages
I am getiing B as my output which I think is not correct. Can someone please suggest. |
|
| Back to top |
|
 |
| madi |
| Posted: Tue Nov 07, 2006 8:04 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
set the transaction mode to yes on the MQOutput node if you want A(no messages)
--madi |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Nov 07, 2006 12:27 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Also, the Persistence property on the queue is just the default. Nonpersistent messages can still be put on the queue.
The automatic on the Input node makes the behaviour different for persistent and nonpersistent messages.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| novice |
| Posted: Sat Nov 11, 2006 7:23 am Post subject: |
|
|
Apprentice
Joined: 20 Jun 2005
Posts: 37
|
| I'm not certain about, but if you catch the exception, the first two messages are committed, since catching the exception means completing the transaction successfully. If you don't catch the exception or you throw another exception in the catch path none of the messages should be in the output queue. |
|
| Back to top |
|
|
| madi |
| Posted: Mon Nov 13, 2006 7:56 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
who said anything about catching the exception?? 
--madi |
|
| 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
|
|
|
|
