Sorry for not getting back to you sooner. With your configuration, messages sent to oldqueuename should be enqueued on oldqueuename and also a new message that's a copy of the original should be enqueued on newqueuename. In both cases, the message will show as enqueued and will only show as dequeued once it is consumed by a consumer that presumably you control.
If messages from either queue are being enqueued but not dequeued, then the first question is, "is the consumer for that queue running (without errors)?" If it's running but no messages are being dispatched to it by the broker, I'd first check the broker's logs, and then attach a JMX viewer to the broker process and confirm (in the MBeans section) that the consumer really is connected to the broker and consuming on that queue. Also, make sure that if the consumer uses a selector, that it matches the messages. Tim On Apr 7, 2017 4:05 AM, "Optimus" <argmishra....@gmail.com> wrote: After doing these changes, I am able to send new messages form ActiveMQ console. But my original task involve sending messages through code not through console. With this configuration messages are stored in new queue and stuck at "Messages Enqueued". Any one have solution for this. -- View this message in context: http://activemq.2283324.n4. nabble.com/Same-messages-to-new-queue-with-new- destination-tp4724608p4724709.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
