XA Transacted JMS session
843830Sep 28 2004 — edited Sep 29 2004Hello,
I'm using a piece of messaging middleware that is based on JMS. I have a problem with the system when using it in xa transaction compliant mode - attempts to receive messages hang. I have access to the middleware's code, and have traced the problem to a line that says:
if (!xaEnable) connection.start();
i.e. if it's xa enabled then don't start the queue! If I modify the code to always start the connection listening on the queue then it works fine. Before I contact the vendor I was wondering if there are any circumstances in which you wouldn't start listening (when you want to receive messages!) - I am not a JMS guru and as not starting the queue seems pretty deliberate I wanted to be reasonably sure of my argument before pressing for a fix.
Thanks for helping.