|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
coordinated transactions WBIMB(V5.0) |
« View previous topic :: View next topic » |
Author |
Message
|
nab054371 |
Posted: Fri Jun 08, 2007 12:00 am Post subject: coordinated transactions WBIMB(V5.0) |
|
|
Disciple
Joined: 15 Nov 2006 Posts: 173
|
Hi,
I got a message flow:
MQINPUT--->COMPUTE1----->DATABASE NODE---->COMPUTE2---->MQOUTPUT.
(And many other nodes in between ....
I have a trace node connected to catch terminal of MQINPUT.
Now here's what perplexes me:
1#) I enabled Transaction(YES) on MQINPUT. Message flow encountered an error in COMPUTE2 node,since the message was transaction oridented,it as traced by MQINPUT catch terminal on backout. -- This makes sense.
2#) I then checked the coordinated transaction check box for this message flow in the bar file that this message flow was deployed to.
This time round ,after having encountered an error on COMPUTE2 ,the message was backed all the way out to the Input queue.This message is now sitting on input queue blocking incoming messages on this queue.I guess I am not sure I necessarily understand WBIMB behaviour and its use in this case ????I would have expected this message to trace on MQINPUT catch node,but obviously it follows a different behaviour.
thanks |
|
Back to top |
|
 |
elvis_gn |
Posted: Fri Jun 08, 2007 1:24 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi nab054371,
I think by checking that in the bar file, you are telling the broker that this flow may be a part of a group of flows(coordinating with other flows in one transaction) which do some common business logic...and if an error occurs, u would want to rollback all the logic that might have been completed in the previous flows, and thus the broker pushes it back onto the queue....
Not sure if the rollback will affect a flow which might have put the msg in this queue in the first place...
OR I could be totally wrong
Regards. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jun 08, 2007 2:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
There is no coordination BETWEEN flows.
The Global Transaction checkbox means that a) You are asking Broker to run the flow in an XA transaction, which means that b) You must have configured your broker qmgr to be the transaction manager for both broker and all application databases.
If you didn't do b) then it's entirely the message went straight to the failure terminal of the MQInput node.
Your best bet, if you don't have your flow stuck in an infinite loop, is to uncheck the box and redeploy the flow and see what happens. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
nab054371 |
Posted: Fri Jun 08, 2007 9:23 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2006 Posts: 173
|
Jeff -
I dont have no infinite loops in my flow..Tried it again,same issue..
thanks |
|
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
|
|
|
|