You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2014/06/23 13:08:25 UTC
[jira] [Created] (AMQ-5241) Spurious WARN FailoverTransport -
Transport .. failed, reason: , attempting to automatically reconnect
java.io.EOFException
Gary Tully created AMQ-5241:
-------------------------------
Summary: Spurious WARN FailoverTransport - Transport .. failed, reason: , attempting to automatically reconnect java.io.EOFException
Key: AMQ-5241
URL: https://issues.apache.org/jira/browse/AMQ-5241
Project: ActiveMQ
Issue Type: Bug
Reporter: Gary Tully
Occasional spurious reconnect from Failover during normal close processing. Incorrectly reporting a problem{code}2014-06-23 12:01:47,095 [0.1:61616@63805] - WARN FailoverTransport - Transport (tcp://localhost/127.0.0.1:61616@63805) failed, reason: , attempting to automatically reconnect
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:258)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:695){code}
Issue is broker response to shutdown info is closing broker end of the socket before client has chance to stop the local transport. So client gets eof before it closes and reports and tries to reconnect in error. Because we treat abortive disconnect as a warn event this can lead to confusion.
--
This message was sent by Atlassian JIRA
(v6.2#6252)