What are you using to figure out that consumers are duplicated? I've seen misleading information in the clientConnectors section of the JMX displays (accessed from JConsole) under ActiveMQ 5.8.0 that sometimes looks like there are more consumers connected than there really are, because it appears to show both prior and current connections, whereas the web console has always had the correct number of currently-connected consumers in my experience. So where you're looking to make that determination matters.
Also, are you using queues or topics, persistent or non-persistent messages (and what message store type), durable or non-durable subscriptions, etc.? More information about your configuration will increase the odds that someone is able to help you figure out what's going on. On Wed, Oct 15, 2014 at 1:00 PM, Annabathula <[email protected]> wrote: > We are using ActiveMQ 5.9.1 over the Azure Cloud. We have a Azure cloud > application that has 4 consumers listening for messages using failover > mechanism . These 4 consumers use message and process these messages > accordingly. The consumers seem to duplicate after a couple of days. > Although it's not always the case, once the duplicate consumers are seen > messages are not been picked up by the consumers anymore. > How can we control and ensure that duplicate consumers are not created? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Consumers-Being-Duplicated-tp4686425.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
