I've got an app that has been using non-XA JMS. I use a single JMS connection, with several sessions, each of which runs in its own thread. When I switched the app to us XA JMS, I started seeing the various sessions use the same thread. Does this sound like expected behavior? Is there any way to get XA JMS to give each session its own thread?
The jms jca ra uses the app server work manager pool to handle processing. Why is this relevant to you?