[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB

[timfox]

"clebert.suconic at jboss.com" wrote : 
  | And regarding to ACKs, I believe we should treat ACK on XA the as nonTransacted/AutoAck.

Well, this is exactly what I have talked about several times and exactly why this thread was originally started.

Let me summarise:

There is a design flaw in the old ASF stuff such that the message is received from the underlying JMS provider *before* it is passed onto the StdServerSession which then, if appropriate, starts a tx and enlists the session.

Therefore when the message is consumed it is an XA session but is not in a session.

This is why we fallback the behaviour of an XASession that is not enlisted to a local tx and when it is enlisted we convert the work done into the global tx.

Originally we were auto_acking, hence messages received in transacted MDBs aren't received in the context of the tx. Ooops. This was the original bug that triggered the thread.

This problem is explained in detail in Mark Little's transaction book. It is not a problem specific to JBoss. I believe that solving this problem was one of the motivations for JCA1.5 message inflow.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040868#4040868

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040868