As said earlier, ActiveMQ's XA support is very poor and should be avoided if you can.
LRC might be the easiest thing to do, otherwise your options are:
- tune the Spring DefaultMessageListenerContainer (it caching can confuse ActiveMQ a lot) and maybe disable BTM PoolingDataSource's cacheProducersConsumers property
- use a different JMS server
- avoid XA.
2011/10/5 MarkFletcher
<mark.fletcher.java@...>
Thank you, James. I appreciate your response. We had some problems with
Atomikos too with the database that we were using. :-)