ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Transaction & Global coordination.

Post new topic  Reply to topic
 Transaction & Global coordination. « View previous topic :: View next topic » 
Author Message
sunny_30
PostPosted: Thu May 17, 2007 8:43 pm    Post subject: Transaction & Global coordination. Reply with quote

Master

Joined: 03 Oct 2005
Posts: 258

Looked at the help center regarding this topic, but wanted to clear up my confusion:

If a message-flow is not Globally-coordinated and whether the messages are persistent or non-persistent, does setting the Transaction properties in the nodes (MQInput,Compute & MQOutput) going to make any difference in the results?

How is the error-flow design going to be impacted when a user-exception is thrown back down the flow? Arent the messages always committed (until the exception point) no matter what the Transaction properties are set in a Globally uncoordinated message flow. Say, when the Transaction-mode of the MQOutput node in flow is set to YES and an exception is thrown down the lane, Isnt the message still outputted to the MQOutput?

Please help.

-Sunny
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat May 19, 2007 6:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

You're confusing 2 topics. Message persistence controls if a message is logged and recovered in the event of a crash. Syncpoint (which may or may not be part of global UOW) controls if a message is rolled back if not committed.

Both persistent & non-persistent messages can be used under syncpoint, or used outside of it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sat May 19, 2007 6:58 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The Transaction properties of nodes control how they interact with transactions. If the *Input node(where appropriate) is not set to transactional, then the flow will never be in syncpoint. If the MQInput node is set to "Automatic", then syncpoint is based on the persistence of the message.

Anything other than an *Input node, the Transaction mode controls whether or not the operation in question is performed in a transaction. Whether or not this is part of the same transaction as the one on the *Input depends on if there IS one on the input, and if the flow is GLOBALLY coordinated or not.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat May 19, 2007 7:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

jefflowrey wrote:
The Transaction properties of nodes control how they interact with transactions. If the *Input node(where appropriate) is not set to transactional, then the flow will never be in syncpoint. If the MQInput node is set to "Automatic", then syncpoint is based on the persistence of the message.


You do learn something everyday.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sunny_30
PostPosted: Sat May 19, 2007 8:30 am    Post subject: Reply with quote

Master

Joined: 03 Oct 2005
Posts: 258

Thanks all for your replies. Very Informative.

I wanted to know how things work when a message-flow IS under syncpoint, and one of the below:
1) Globally Co-ordinated.
2) NOT Globally Co-ordinated.

Lets assume the message-flow:
Quote:
MQInput -> FlowOrder -> (first-out) -> Compute -> MQOutput
-> (second-out) -> Throw


Message flow is under Transaction.
Quote:
MQInput Properties: TransactionMode -> YES
Compute: Transaction -> Automatic
Say, 3 messages are propagated out of Compute to MQOutput.
A DB_Insert is made for each propagation.
MQOutput: Transaction -> YES


Im assuming that the THROW node generates a flow exception.

My questions are:

*If the Message-flow is Globally co-ordinated, Are all the 3 propagates & 3 DB-Inserts rolled back? I assume YES.
*If the Message-flow is NOT Globally co-ordinated, Are all the 3 propagates & 3 DB-Inserts rolled back? I assume NO.

Please let me know if Im right.
Thanks,
-Sunny
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Transaction & Global coordination.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.