There is a slowConsumer advisory that contains the consumer info that has the consumerid which is based off the connection id. org.apache.activemq.advisory.AdvisoryBroker#slowConsumer
Also have a peek at the abortSlowConsumerPolicy, this provides a way to kill off slow consumers The implementation of that policy may be of interest. You could provide your own variation of a slow consumer policy. http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/AbortSlowConsumerStrategy.java http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/broker/policy/AbortSlowConsumerTest.java On 18 July 2012 21:47, kureckam <[email protected]> wrote: > I've been dealing with Out Of Memory issues and I believe it may be due to a > slow or hung consumer. The software has about five different Topics with > multiple producers/consumers for each topic. I've been playing around with > it and simulated a slow consumer which caused the problem to occur. I > noticed via JConsole that a subscriber is created for each consumer and the > slow consumer showed a dispatchedQueueSize greater than zero where the > others remained at zero. Given this I believe I may be able to use this to > determine if a consumer is slow or hung but I can't find a way to correspond > the consumer to the subscriber. I would appreciate how I can correlate the > two or another way of programmically determining if a consumer is going slow > and which one it is. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Finding-a-slow-consumer-tp4654153.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
