Yes this was "fixed" in 1.3.0, so an XA session which is not enlisted in a JTA tx falls back to acting as non transacted (auto_ack).
The whole story is rather complex. For some use cases (like the reported one) an XASession needs to act as non transacted when not enlisted in a tx. But in other situations we have to act as transacted! E.g. when the XASession is being used to consume messages for an MDB. In this case messages can be consumed by the connection consumer before the session is enlisted. In this case it needs to act as transacted so when the session is finally enlisted any work done before the enlisting is converted into the JTA tx. So in other words, we have to someone work out if the session is being used for an MDB (also for the message bridge) and act differently. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086676#4086676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086676 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
