The next thing I'd do is the suggestion from my earlier email to use JMX to see what the broker thinks is going on with that queue.
I'd also confirm that the consumer is properly configured to ack messages, either via auto-ack (the default behavior) or via some form of manual acks (check that your algorithm is working right if you're doing this). On Apr 13, 2017 6:53 AM, "Optimus" <argmishra....@gmail.com> wrote: > Hi Tim, > > I have verified that we have connected and working consumer for both > queues. > But still messages were not processed. ActiveMq.log file is not point > towards any warning or error during this transaction. > > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Same-messages-to-new-queue-with-new- > destination-tp4724608p4724929.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
