You can use security+ACL to control who has access to consume which queues:
http://activemq.apache.org/security.html You can also use exclusive consumer to make sure one consumer is listening: http://activemq.apache.org/exclusive-consumer.html On Tue, Jan 28, 2014 at 12:08 AM, vkcse <[email protected]> wrote: > Hi, > > I am using ActiveMQ 5.8 and to consume the queue data via code I created one > consumer and I stop/restart the consumer app and activemq when > required(without cleaning the kahaDB directory). Recently what happen is > some messages are stucked in queue itself instead of consuming when I gone > through the jconsole to see what happen I came to know that we have 2 > consumers instead of one, if queue dispatch messages to one of the consumer > it is processing fine if the queue dispatch message to another it is not > processing those. Is there any chance of consumer expire/inactive? and Is > there any way to avoid this situation or to process only to active consumer? > > Thanks, > Krishna. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Inactive-Expired-CONSUMER-tp4676865.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
