Re: javax.jms.JMSException: Cannot send, channel has already failed: tcp://127.0.0.1:61616

[Madhu <mc...@incomm.com>]

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

Re: javax.jms.JMSException: Cannot send, channel has already failed: tcp://127.0.0.1:61616

[Tim Bain <tb...@alumni.duke.edu>]

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 there are probably others.

If your symptoms aren't being caused by a TCP port check, I recommend you
describe your symptoms in detail, because with your current description
there's not enough detail for anyone to guess what the root cause is.

Tim

On Sep 17, 2017 5:39 PM, "Madhu" <mc...@incomm.com> wrote:

> 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
>

Re: javax.jms.JMSException: Cannot send, channel has already failed: tcp://127.0.0.1:61616

[Madhu <mc...@incomm.com>]

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