Home/ Questions/Q 4557544
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T17:31:25+00:00

Could someone please confirm if I’m right or wrong on this. It seems to

  • 0

Could someone please confirm if I’m right or wrong on this. It seems to me that “selector” operation is done within MessageConsumer implementation. (i.e. ALL messages are still dispatched from Message Broker to MessageConsumer and then “selector” operation are performed against those messages). The problem occurs when we have a bunch of messages that we are not interested in (i.e. not match our selector), those messages will eventually fill up MessageConsumer’s internal queue due to prefetch or cache limit. As a result, we will not be able to receive any new messages, particularly the ones we’re interested in with the selector.

So, is there a way to configure AMQ to perform the selector operation on MessageBroker side? Should I start looking at “interceptor” and create my own BrokerPlugin? Any advice on how to workaround this issue?

I’m really appreciate any answer.

Thanks,
Soonthorn A.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Selectors actually are applied at the broker, not on the client side. If your selector is sparse and the destination sees a lot of traffic its likely that the broker has not paged in messages that match the selector and you consumer won’t see any matches until more messages are consumed from the destination.

    The issue lies in the Destination Policy in play for your broker. By default the broker will only page in 200 message for a browser to avoid using up all available memory and avoid impacting overall performance. You can increase this number via your own DestinationPolicy in activemq.xml, see the documentation page here.

    • 0