when you open a socket to the broke port, there are a series of protocol negotiations expected, and this can cause errors if the protocol isn't followed. you may try stomp transport for your telnet session? a tcp port check could cause those errors because port is opened/closed or even just half-opened (SYN port scan) before the broker can respond.
On Wed, Jun 26, 2013 at 3:53 PM, jliao <[email protected]> wrote: > I'm using ActiveMQ 5.5, and I have some monitoring going against the broker > port to perform a TCP port check, and somehow I'm getting all these errors > in my logs: > > > WARN | 06-26-2013 15:00:41.055 | Async Exception Handler | > org.apache.activemq.broker.TransportConnection.Transport(202) - Transport > Connection to: /10.20.30.40:51534 failed: > org.apache.activemq.transport.InactivityIOException: Cannot send, channel > has already failed: /10.20.30.40:51534 > WARN | 06-26-2013 15:01:40.715 | ActiveMQ NIO Worker | > org.apache.activemq.broker.TransportConnection.Transport(202) - Transport > Connection to: /10.20.30.40:51545 failed: java.io.EOFException > WARN | 06-26-2013 15:01:40.715 | Async Exception Handler | > org.apache.activemq.broker.TransportConnection.Transport(202) - Transport > Connection to: /10.20.30.40:51545 failed: > org.apache.activemq.transport.InactivityIOException: Cannot send, channel > has already failed: /10.20.30.40:51545 > WARN | 06-26-2013 15:02:40.502 | ActiveMQ NIO Worker | > org.apache.activemq.broker.TransportConnection.Transport(202) - Transport > Connection to: /10.20.30.40:51561 failed: java.io.EOFException > > > The 10.20.30.40 is the IP for the ActiveMQ broker, and the TCP port > checking > is 61656. This error can be repro by just simply doing a "telnet > 10.20.30.40 > 61656". So does anyone know what might be causing this error? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-transport-error-when-I-do-a-telnet-check-on-the-port-tp4668611.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
