[AMQ-5241] Spurious WARN FailoverTransport - Transport .. failed, reason: , attempting to automatically reconnect java.io.EOFException

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.10.1, 5.11.0
• Labels: Failover WARN
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 23/Jun/14 11:08
• Updated: 13/Jul/16 18:15
• Resolved: 23/Jun/14 11:24

Description

Occasional spurious reconnect from Failover during normal close processing. Incorrectly reporting a problem

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)

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.