Re: "queuePrefetch" policy doesn't seem to be working properly

This is expected behavior. When a message with a JMXGroupId is dispatched to a consumer, that consumer is the sole one that will receive future messages with the same JMXGroupId, until the connection from the consumer to the broker is broken. Here's your sequence of events, with additional comment

Re: "queuePrefetch" policy doesn't seem to be working properly

Thanks for the quick response. I am using ActiveMQ 5.15.10 and we are connecting to activemq using MuleSoft which is running on 3.9.0 runtime version. I have set the queue prefetch at the connection level (not at the broker) like below. tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1 I

Re: "queuePrefetch" policy doesn't seem to be working properly

Hi, I guess it’s the same as https://issues.apache.org/jira/browse/AMQ-7418 right ? I was about to add a comment in the Jira. I would need the version from both broker and client. Do you have prefetch defined on broker side ? Anyway, the scenar

"queuePrefetch" policy doesn't seem to be working properly

Hi, We are using ActiveMQ and MuleSoft in our project. We connect to ActiveMQ from MuleSoft. As per the project requirement, we are using JMXGroupId and Queueprefetch polcy. We have set Queueprefetch to 1 at the connection broker url like below and number of consumers are set to 2 tcp://localh