Two things to look at. As mentioned above, not ack'ing is one of them. If the session is setup to auto-ack, then that's not the issue. If the session is set to client-ack or transacted, then it needs to ack the messages or the queue will eventually fill up.
Another possibility - look at the queue for messages that do not match any active consumer selectors. If the queue gets more than 200 (max page size setting) of the same, it will stop dispatching messages until that number drops below 200 again. -- View this message in context: http://activemq.2283324.n4.nabble.com/Issue-with-MessageConsumer-and-MessageSelector-tp4704870p4704935.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
