We see the same error, sporadically, we feel it's caused by load-balancers
momentarily directing JMS clients to slaves on initial connect during a
master failover situation, at least that's our best guess.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I suspect that multiple things can cause these symptoms. One of them
(according to
https://serverfault.com/questions/550735/activemq-cannot-send-channel-has-already-failed-every-2-seconds)
is having a TCP port check of the sort you might use to monitor whether a
broker is alive. I expect that
We are looking for a solution for this issue, appreciate your help
Thanks,
Madhu
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I am facing the same issue, were you able to fix this.
Thanks,
Madhu
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
:61616
And the gateway-XX child container then sends the petition to the correct
mq-XX. (Master)
The problem I'm seeing is that, sometimes a random gateway-XX child
container, throws an exception:
javax.jms.JMSException: Cannot send, channel has already failed:
tcp://127.0.0.1:61616
And we
