activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Consumer is not able to pick messages from queue
Date Thu, 09 Sep 2010 11:29:59 GMT
yea, this is a known issue with sparse selectors. increasing the
maxPageSize via a destination policy entry for that queue will help as
it will ensure that more messages are held in memory for dispatch.

see: the comments on and

On 8 September 2010 18:44, manua <> wrote:
> Hi All,
> I am working on request-response system, where all the requests are posted
> on a single queue with different selectors. There are multiple consumers
> listening on the queue.
> When the load is low, this works fine. Each consumer is able to process the
> respective message. But if the load is high and there are pending messages
> of one type in the queue, other consumers timed out without picking the
> message from the queue. If I didn't allow the consumers to time out, then
> they will wait till all the previous messages are processed and then process
> their respective messages.
> To give little more idea,
> There are around 10000 messages in the queue with selector type A and four
> consumers with selector A are running.Consumers for type A message took
> around 2-3 seconds to process each message. When there are 10000 messages
> pending in the queue, another 5 messages with selector B and selector C are
> added to the queue.There are two consumers running for type B and one for
> type C, each with a timeout of 60 seconds.
> But, consumers B and C never got the messages and timed out.
> Is it possible that due to the other messages in the queue, B and C are not
> processed. Or there is some other setting that needs to be set.
> Please let me know your inputs.
> Thanks,
> Manu
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


Open Source Integration

View raw message