| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WAS and WMQ 5.3 Extended Transactional Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| szudor |
 Posted: Tue Jan 04, 2005 11:31 am Post subject: WAS and WMQ 5.3 Extended Transactional Client |
 |
|
Novice
Joined: 21 Apr 2002
Posts: 18
Location: Budapest
|
Hi,
We have a probleme using WAS coordinated transactions with the Extended Transactional Client.
The environment:
WebSphere MQ V5.3 CSD 7
WebSphere MQ Extended Transactional Clients V5.3.0.2
WebSphere Application Server V5.1.1
Windows 2000 SP4 Professional
Abstract:
In case of client binding and XA, if the application server crashes, message is lost.
Our application needs to access MQ and database in the same transaction, therefore we configured both JDBC and JMS resources to use XA. The relevant part of the application runs in an MDB and updates a database. The
application runs in a clustered environment in order to provide fail-over capability. One of our requirements specifies that in case one of the application servers crash the other application server must continue by
processing the same message. Therefore we need to use client binding to a remote, HACMP-supported MQ server.
We found that
- In case of binding/XA mode and client/non-XA mode the message is returned to the queue after the crash of the application server. The message is not lost.
- In case of client/XA mode the message is not returned to the queue. The message is lost.
If the application server is not killed but the MDB throws and exception, the message is returned to the queue in all cases. The problem is only in the case of ther crash of the application server.
We try to use the KeepAlive=YES, ClientIdle=25 options also, but the result are the same.
Any idea ?
_________________
Sandor Zudor,
Certified Solution Expert/Developer
IBM WebSphere MQ & Message Broker |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Jan 04, 2005 1:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you sure the message is lost and not just hidden in the unresolved transactions layer ?
Have you used the transaction tools from MQ and performed a rollback of any uncommitted transaction after server crash ?
Enjoy  |
|
| Back to top |
|
|
| szudor |
| Posted: Tue Jan 04, 2005 9:42 pm Post subject: |
|
|
Novice
Joined: 21 Apr 2002
Posts: 18
Location: Budapest
|
Yes, I'm sure.
In our intention, the main goal of this architecture are that the message will be rolled back, and the MDB running in the second (on-line) WAS environment will process this message.
In fact, the message are lost.
_________________
Sandor Zudor,
Certified Solution Expert/Developer
IBM WebSphere MQ & Message Broker |
|
| Back to top |
|
|
| slaupster |
| Posted: Wed Jan 05, 2005 4:28 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2004
Posts: 41
|
It is highly unlikely that the message is in fact lost. It is exactly this that MQ and XA mean to get right.
If the MDB has in fact picked up the message in non-xa consumption and then the server crashes, the message will NOT be returned to the queue, as before the MDB is invoked with the message, it has been removed from the queue. In XA consumption, the message never in fact leaves the queue until the tran is committed, but it will not be visible to other apps. If the tran is still unresolved you can see this with dspmqtrn command, but there is a timeout associated with the tran, and it will roll back after the timeout expires.
If you are convinced that the message is in fact lost I would get trace and open a PMR. There is no point looking for a work around as it will not be reliable. |
|
| 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
|
|
|
|
