There are two things that happen with message groups that makes them a poor match for use with selectors.
First, the default implementation of message groups uses "buckets" of assignments for groups-to-consumers. This means that multiple groups actually get assigned to the same consumer because the group name shares the same hash. SO, it is entirely possible to have a message group assigned to a consumer whose selector does not match. Second, even if that were not the case, all messages within a single group are dedicated to a single consumer, based on the group name. Any messages that do not match that consumers selector but are in the same group will sit unconsumed, filling up the max-page-size limit (defaults to 200). -- View this message in context: http://activemq.2283324.n4.nabble.com/Selective-consuming-of-priority-messages-with-message-groups-tp4704813p4704937.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
