| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Commiting in compute node |
« View previous topic :: View next topic » |
| Author |
Message
|
| shassey |
 Posted: Wed Oct 01, 2003 10:57 am Post subject: Commiting in compute node |
 |
|
Apprentice
Joined: 25 Dec 2001
Posts: 25
Location: shassey
|
I have a flow where there are two different compute nodes. One accesses db2 on one server and is configured to commit at the node and the other compute node is configured to commit as well and it accesses stored procedures on os/390. I would expect that if the message flow fails that because both nodes had commit on them that nothing would be rolled back. I have found that the stored procedure updates on os/390 are commited perfectly and do not roll back on failure and the other compute node does roll back. I am not sure I understand why since each node is told to commit each time the node executes.
ideas? |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Oct 01, 2003 8:53 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Can you tell us how your nodes are arranged in your message flows. Can you provide us your environment details?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Craig B |
| Posted: Thu Oct 02, 2003 3:36 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
One thing to check for in these situations is that the second compute node actually executed in the flow. If an error occurred at some point in the message flow, then it might never have reached the second compute node that has this other database activity. If this is the case then this would mean no updates ever occured. You have to be careful to distinguish between no updates at all, and those updates that were held in a Unit of Work and then rolled back.
_________________
Regards
Craig |
|
| Back to top |
|
|
| shassey |
| Posted: Thu Oct 02, 2003 11:55 am Post subject: Committing in compute node |
|
|
Apprentice
Joined: 25 Dec 2001
Posts: 25
Location: shassey
|
We are running WMQI 2.1 CSD03 on aix. mqseries 5.2 csd05, udb7.1 fixpak 5.
1. The first compute node - accesses db2 tables on the same aix machine the broker is running on. It is set to commit (2 tables).
2. use routetolabel to either a compute node which is set to commit and accesses a db2 stored procedure on os390 or a label which writes to a queue and then a compute which runs a db2 stored procedure on os390 - set to commit.
Each of the db2 mainframe stored procedures commit, the local does not. You can also tell that the local is not commiting because as this runs - (it is iterative driven by one message using propogate) - you can do a select count(*) on local table and you get a time out. Where I can select on the mainframe db2 table that the stored procedure is updating and I can select just fine. |
|
| 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
|
|
|
|
