Thanks for the response. While that explains a lot, I'm confused as to why it
was implemented that way - i.e., trying to preserve the message order.
Firstly, if I have 10 JMS consumer threads and only 5 messages, there's a
great chance that the order will not get preserved anyways. Secondly, if
cod
I seem to be seeing something entirely unexpected - when my JmsConsumer
thread throw a SchedulerException, that JmsConsumer thread will not process
any new message until it has finished processing the original ActiveMQ
message. I was expecting that having a delay would mean that that
JmsConsumer th
