I had thought that once the message cursor became full of messages for the
other selector (because there's only one cursor for a given destination),
no more messages could be paged in till some of those others were consumed,
but that might not be right (and I'm curious to hear what your code
inspec
Hello,
I'm looking for a message pattern - something like message groups. I would
like to have one or more consumers/workers that process messages from a
queue, each message is tied with specific device and needs to be processed
in the order received on a per-device context, so at one time only on
Which environment do you have? Are you using an application server with
ActiveMQ RAR or are the clients running standalone?
We had recently a problem with a message driven bean (Glassfish+ActiveMQ
RAR), which stopped acknowledging messages and they were accumulating in the
queue. All the messages
tbain98 has the right idea. And that raises an interesting question
regarding messages on-disk and not in-memory - I need to review to see how
that operates.
Here's how I expect it to work: the consumer with it's exclusive selector
will get all pending messages which match its selector regardless
Hi
I would like to know what the expected state after a successful
master/slave failover is. The AMQ website seems to be inconsistent or at
least not very accurate in this topic.
The general master/slave page with the different flavours listed, says for
all types "Automatic recovery of old maste
Hello,
We're using ActiveMQ 5.10.0.
About a month ago we noticed that one of our queues started overflowing.
There was no apparent reason: the consumers didn't seem slower than
normally, the messages from the producers were also not arriving any faster
than normally. But still the messages were get
