If you don't trust your own counters just use the ConsumerEventSource, it provides a reliable count for you. If you want to have some timeout condition, you could do your own client side timeout. There are lots of ways to do this, but a recent idea to help with this is beanflow, see: http://servicemix.org/site/beanflow.html It supports adding simple workflow style timeouts.
On 5/24/06, himmeric <[EMAIL PROTECTED]> wrote:
Thanks I was considering that, but didn't trust the integrity of my own internal counter. Since shutting down a producer when there are still consumers would be very bad. For now I'm using the command line query tool to check for periodic ConsumerCount=0. Maybe a better approach would be to use the ConsumerListener class for an internal counter with a periodic sanity check using command line tool to make sure I didnt shut down something I hadn't. This could probably be done with JMX too, but I got lost pretty quickly in that (new to jmx). I opened a feature request here: http://issues.apache.org/activemq/browse/AMQ-723 -- View this message in context: http://www.nabble.com/Problem+with+No+Subscriber+Advisory+Topic-t1621608.html#a4551149 Sent from the ActiveMQ - User forum at Nabble.com.
-- Regards, Hiram
