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

[timfox]

"adrian at jboss.org" wrote : 
  | 
  | There is actually nothing in the spec about this behaviour.
  | The XA stuff is massively underspecified in the JMS spec.
  | And of course it is optional whether a JMS impl supports XA.
  | 
  | The JBossMQ behaviour is to assume that an XASession behaves like
  | AUTO_ACKNOWLEDGE when the XASession is not enlisted in a JTA transaction.
  | (Some JMS implements throw an exception in this case).
  | 
  | 

We are having some issues with TCK where it seems the TCK actually tests this situation - the behaviour it expects is the same as the JBossMQ gives :)

anonymous wrote : 
  | There is one exception to this. When the XASession is being used as part of
  | a ServerSessionPool, the semantics need to be receive then enlist.
  | So for this, the XASession behaves like there is a transaction, it will be told
  | later what XID to use for the 2PC protocol.

What I don't quite understand is how the session knows it has been created via a session pool rather than any other way so it can have different behaviour.

I couldn't work out immediately from the JBoss MQ code how this info is passed to the session.

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

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