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
Thank you Tim for your response.
When I an mqtt transport connector to my broker-config "
" and I try to
connect to it using apache paho java, I am getting this exception :
Exception in thread "main" java.lang.IllegalArgumentException:
mqtt://0.0.0.0:1884
at
org.eclipse.paho.clie
The TCP transport speaks OpenWire, so it's not valid to connect to it with
an MQTT client.
Tim
On May 18, 2017 3:07 AM, "aragoubi" wrote:
I have an embedded broker, and I am connection a Paho client to it.
This my broker config file :
http://activemq.apache.org/schema/core"; useJmx="true"
us
I have an embedded broker, and I am connection a Paho client to it.
This my broker config file :
http://activemq.apache.org/schema/core"; useJmx="true"
useShutdownHook="false" brokerName="mimo.broker1">
I am getting t
; there has always been something else that failed, and then you hit the
> > >> error you quoted. Are there any earlier errors in your log files
> (either
> > >> client or broker)?
> > >>
> > >> Tim
> > >>
> > >> On Mar 31, 2
du"
> wrote:
> >>
> >> I am doing my application setup in linux for the first time. I have
> both a
> >> standalone java program and active mq running on Linux.
> >> I am trying to connect to Active Mq (5.13) but I keep getting an error
> >> message "*cannot send channel has already failed*"
> >>
> >> The same program working fine in my local windows machine (when I run
> >> standalone java & active mq in my local).
> >>
> >> Please advise.
> >>
> >> --
> >> Shekhar
> >>
> >
>
gt;> On Mar 31, 2017 5:36 AM, "Shekhar Naidu" wrote:
>>
>> I am doing my application setup in linux for the first time. I have both a
>> standalone java program and active mq running on Linux.
>> I am trying to connect to Active Mq (5.13) but I keep getting an e
ve mq running on Linux.
> I am trying to connect to Active Mq (5.13) but I keep getting an error
> message "*cannot send channel has already failed*"
>
> The same program working fine in my local windows machine (when I run
> standalone java & active mq in my local).
>
> Please advise.
>
> --
> Shekhar
>
; wrote:
I am doing my application setup in linux for the first time. I have both a
standalone java program and active mq running on Linux.
I am trying to connect to Active Mq (5.13) but I keep getting an error
message "*cannot send channel has already failed*"
The same program working
I am doing my application setup in linux for the first time. I have both a
standalone java program and active mq running on Linux.
I am trying to connect to Active Mq (5.13) but I keep getting an error
message "*cannot send channel has already failed*"
The same program working fine i
: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 w
Hi,
I am getting the following error.
<http://activemq.2283324.n4.nabble.com/file/n4716873/JMeter_Error_9-23-2016.png>
Let me know.
Thanks
Ram.S
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Cannot-send-channel-has-already-failed-messages-tp4654848p471687
Hello:
I'm using AMQ 5.8.0 and I'm getting a lot of messages as
INFO | jvm 1| 2013/11/13 03:42:07 | ERROR | Could not accept
connection from null:
org.apache.activemq.transport.InactivityIOException: Cannot send,
channel has already failed: tcp://127.0.0.1:44506
in broker&
.1:37501 failed:
org.apache.activemq.transport.InactivityIOException:
Cannot send, channel has already failed: tcp://127.0.0.1:37501 |
org.apache.activemq.broker.TransportConnection.Transport | Async Exception
Handler
org.apache.activemq.transport.InactivityIOException: Cannot send,
channel has already failed: tcp://
We are using Version 5.6.0 in an "JDBC Master Slave" configuration. From time
to time we get the following messages:
tcp://10.55.205.243:35530 failed:
org.apache.activemq.transport.InactivityIOException: Cannot send, channel
has already failed: tcp://10.55.205.243:35530
Sometime thi
18 matches
Mail list logo
