| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| a two phase commit problem: WMQ JMS, WebLogic, and Oracle |
« View previous topic :: View next topic » |
| Author |
Message
|
| bearsonli |
 Posted: Tue Mar 02, 2004 9:48 am Post subject: a two phase commit problem: WMQ JMS, WebLogic, and Oracle |
 |
|
Novice
Joined: 02 Mar 2004
Posts: 16
|
Hi,
We have an Enterprise application built in WLS7.0 that reads/writes msgs from/to WMQ 5.3, and also updates Oracle 9.2. WMQ and WLS reside on the same Solaris box, while Oracle is on a different machine. Furthermore, the WMQ JMS objects (XAConnFactory etc) are put onto the WLS JNDI tree using a WMQ Startup Class.
WLS is the txn manager in this global txn, which uses container managed txn, and has three stateless session beans with the first doing a MQGet, the second updating the DB, and the third doing a MQPut.
If the txn needs to rollback due to, for example, DB errors, the MQGet and DB part will be rolled back successfully. However, the MQPut can't be rolled back.
We have tried to use the same or two different MQXaConnectionFactory for the MQGet and MQPut beans, and got the same result.
Any ideas?
Regards,
Yutao
MQ and WLS Admin |
|
| 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
|
|
|
|
