WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
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.