An application will exit when no more non-daemon threads exist. I don't
know whether the failover thread is a daemon or non-daemon thread, but you
could attach a debugger to your producer and connect to the iterate()
method of the Task created in
FailoverTransport.FailoverTransport.FailoverTranspo
Hi,
I am not expecting my producer to exist after it looses connection from
broker. I want my client to stop when I want them to stop, but with producer
its not happening. I had to do a kill -9 pid to stop the process (kill pid
is not working). Am unable to understand this behaviour of producer.
The failover transport's behavior is "connect to any one of the URIs in
this set; if that connection dies, try connecting again to any URI in the
set." By default, the failover transport will log if it is unable to get a
connection to any of the URIs, and then wait for a while and try again.
When
I have tried with failover broker as well
('failover(tcp://host1:61616,tcp://host2:61616)'), but still same problem.
What could be reason for this.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Unable-to-stop-producer-tp4686340p4686346.html
Sent from the ActiveMQ - Use
