Andrew,
That's a very good point.
Here's a tiny m2 based project to reproduce the error:
my-app.zipThe main class can be run from eclipse, its called EnqueueingClient.
This starts up activemq and mule.
The eclipse project can be generated by the m2 eclipse plugin.
It initially sends one message to the queue.
You can also send messages via the JMX console for ease of use (its bound to the namespace foo).
Thanks for your help,
Ben
Andrew Perepelytsya wrote:
I know there were issues with queue browsers in ActiveMQ before. Not that it
wasn't fixed by v4 (I just don't know now). Before that it resulted in
messages getting reordered randomly.
The problem will need some investigation. Could you also list the activemq
config file. Generally, the easier you make to reproduce the scenario (test
client, etc.) the higher the chances are you'll get feedback.
