We have consumer on a queue in our project and spring's ScheduledTimerTask which closes, releases reference on it, then creates and starts a new one periodically (ones per 6 hours). When application stays idle for a long time and consumer stays idle too, ConsumerInfo shows number of consumers > 1. Then we put message in queue and after that number of consumers becomes 1. Why does ConsumerInfo show wrong number of consumers? Can broker hold dead references on consumers and destroy them only if message enters queue?
ActiveMQ 5.1.0 Windows XP -- View this message in context: http://www.nabble.com/ConsumerInfo-shows-wrong-number-of-consumers-tp21910192p21910192.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
