Another solution is for the JCA layer to be clever enough to realise there is no
transaction and execute the jms operations using a standard Session rather than an
XASession, then we avoid these problems.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968791#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...