There is no ordering guarantee in this case, as each destination will
do an independent dispatch.
Ordering is per destination only so messages from C and D will be interleaved.
When there are a pool of consumers, by default dispatch will round
robin push to each consumer.
You can change this
I've been able to successfully reproduce the issue in a dev environment,
but it's hard to identity exactly what is causing it. It is almost like it
is a race condition of some kind.
On Wed, May 16, 2012 at 10:27 PM, Gary Tully gary.tu...@gmail.com wrote:
sorry, yes, there is one more piece to
We are upgrading from AMQ 5.4.0 to 5.6.0, and noticed two issues right off the
bat:
- The activemq-all-5.6.0.jar library is now bundled with the SLF4J Log4J
binding, trumping the JDK 1.4 binding already in our classpath. As a
workaround we have switched to using the individual libraries
