MQSeries.net :: View topic

RegSherwood · Posted: Wed Sep 16, 2009 11:53 am Post subject:

Hi

I am not overally familiar with MQ and transactional processing but am hoping someone can at least point me in a direction.

What I am trying to deal with is the configuration of a MQ Series so that it is involved in global transactions (XA) - so far I have had little luck in finding clear documentation around this.

My env is comprised of the following:

DB - MS SQL Server 2005

BEA WLS 8.1 Node 1
contains MDBs (uses session beans)
MDB 1
MDB 2
BEA WLS 8.1 Node 2
contains MDBs (uses session beans)
MDB 1
MDB 2

MQ Series Server V7.0

What I want to setup is MQ so that it particpates in the global transaction that is happening on the BEA nodes. I see references in the MQ Explorer to XA Resource manager - and asking about switches and such - but I am at a loss to understand what gets placed in there.

What I am trying to determine (if it's possible) is the following scenario:

A JMS message from a client is placed on a queue - MDB1 (on either Node1 or Node 2) polls for messages and one of the MDB1s receives the message. During the processing of MDB1 it performs numerous DB updates - the final step in MDB1 is to place a NEW JMS message onto another JMS queue. This new message will be processed by MDB2 (Node 1 or Node 2). But, I don't want MDB2 to start processing of this message until after the MDB1 database changes are written to within its transaction. If the updates to the database fail (for whatever reason) I want the new JMS message removed from the queue. Currently, the original JMS message receives a runtime exception and is placed back on the original JMS queue and will be processed again... but, MDB2 has received the new message and has attempted to process it anyways.

Does the MQ have the capability to block the concept of a dirty read within its transactional model. or am I off my rocker here from a transactions point of view around JMS message creation.