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
Some observation :
I saw this exception in ActiveMQ setup again. This time I restarted broker
with "AllowLinkStealing" and issue got resolved.
Again I restarted broker with normal configuration (without
"AllowLinkStealing"), I didn't see the issue.
Can I use "AllowLinkStealing" for workaround
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
.
*[20141013 12:27:12.469 IST (ActiveMQ Task-3)
org.apache.activemq.transport.failover.FailoverTransport#getConnectList 804
DEBUG] - urlList connectionList:[tcp://host:61616], from: [tcp://host:61616]
[20141013 12:27:12.470 IST (ActiveMQ Task-3)
org.apache.activemq.transport.failover.FailoverTransport
