activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benj <apache....@benandi.com>
Subject Re: ActiveMQ slow consumer policy
Date Fri, 21 Dec 2012 15:11:35 GMT
Thanks - nms.prefetchPolicy.topicPrefetch=1 did the trick.
I'm seeing fairly long latencies - upto about 500ms, and the broker is using
over 500MB of memory. But it is managing the queues properly.


gtully wrote
> I had a peek that your code, the problem is on the broker.
> The problem is that the prefetch value specified in broker config via the
> policy entry is not enforced by stomp, so the default topic prefetch value
> (maxInt-1) is in effect.
> You could validate that via jconsole jmx on the broker, looking at the
> topic subscriptions actual prefetch values. we want them to be 1
> 
> To workaround this, you need to specify the topicPrefetch via your client.
> Either set the policy on the connection factory or via the brokerUrl nms.
> url params.
> 
> A client supplied value will take effect and you should not see the build
> up of messages on slow subscriptions.
> 
> I opened https://issues.apache.org/jira/browse/AMQ-4234 to track this.





--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-slow-consumer-policy-tp4660859p4661011.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message