A known issue with ActiveMQ? Is there a ticket somewhere or some documentation outlining the details? Does Is there any workaround short of not using the default Spring container? Does the issue exist with ActiveMQ 4.x? If not, maybe we could just try using that version as opposed to reimplementing our listeners.
We're experiencing the same issue in a slightly different context: multiple containers with 1 concurrent consumer in different JVMs accessing the same queue. rajdavies wrote: > > This is a known issue - please use the latest snapshot > -- View this message in context: http://www.nabble.com/ActiveMQ-5.0.0-AMQ-Message-Store-fails-when-using-with-Spring-DefaultMessageListenerContainer-with-more-than-1-concurrentConsumers-to-dispatch-JMS-messages-from-Queue-tp14805901s2354p14882065.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
