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. On 19 December 2012 16:25, benj <apache....@benandi.com> wrote: > That would be really helpful - thank you! > > Here's a zip with the VS2012 solution containing producer/consumer > projects, > as well as my activemq.xml: 201212activemqtest.zip > < > http://activemq.2283324.n4.nabble.com/file/n4660906/201212activemqtest.zip > > > > I was running this between two machines, so you'll need to change the URI > that the consumer connects to, unless your machine happens to be called > benlaptop :-) > > Thanks, > > Ben > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-slow-consumer-policy-tp4660859p4660906.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://redhat.com http://blog.garytully.com
