To get expected result, I followed below two steps :-
1. I observed log files that shows which hint towards some corrupt or
partial deployed ActiveMQ. SO, I took back up and reinstall the ActiveMQ
2. Below are my final changes in activemq.xml
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
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-messa
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 dequeu
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 th
@Tim Thanks for sugegstions
The way I have achieved this is
Step 1:- Making a new queue which take data of existing queue
Step 2 :- Adding consumer for newly created queue
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-messages-to-new-queue-with-
I'd use a composite queue:
http://activemq.apache.org/virtual-destinations.html (near the bottom)
Tim
On Apr 6, 2017 8:11 AM, "Optimus" wrote:
I am currently working on a task which involve functionality of sending
duplicate messages to new queue which is directing to fresh location.
The scena
