activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reynald Borer <>
Subject Re: 5.4.1 Older Messages Blocking Delivery
Date Tue, 11 Jan 2011 20:41:41 GMT

You can increase the maxPageSize parameter on a per destination policy. By default it is defined
to 200, which means that (as far as I understand) the broker will keep information on 200
messages per destination, the other messages being paged to disk. Of course it will increase
memory usage, and there are probably going to be other side effects I am not aware of. Check
out for more information.

As a good advice, I would consider in your case if using a specific destination for each message
selector might not be a better idea. Combined with a well formed set of Camel rules, you'll
have to modify nothing in your producer code, only the consumers will have to be adapted to
use the correct destinations.


On Tuesday, January 11, 2011 at 21:20 , urciolo wrote:

> I have a situation where older messages are blocking the delivery of newer
> messages in a queue. A consumer is using a message selector that matches
> the newer messages, but not the older messages. This seems to happen with
> just a couple of thousand messages that do not match the message selector.
> Is there a configuration parameter that would have activemq look at more
> messages, so say I could have tens of thousands of queued messages and still
> have newly delivered messages consumed using the message selector?
> Thanks.
> -- 
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message