You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Trejkaz (JIRA)" <ji...@apache.org> on 2016/03/10 05:03:40 UTC
[jira] [Commented] (AMQ-5241) Spurious WARN FailoverTransport -
Transport .. failed, reason: , attempting to automatically reconnect
java.io.EOFException
[ https://issues.apache.org/jira/browse/AMQ-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188633#comment-15188633 ]
Trejkaz commented on AMQ-5241:
------------------------------
I see the same stack trace being output a lot to System.out during our test runs, even though we don't log to System.out and we're already updated to v5.13.0.
Maybe ours aren't spurious but it isn't clear how I am supposed to know.
{noformat}
[java] java.io.EOFException
[java] at java.io.DataInputStream.readInt(DataInputStream.java:392)
[java] at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
[java] at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240)
[java] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232)
[java] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215)
[java] at java.lang.Thread.run(Thread.java:745)
{noformat}
> 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
> Assignee: Gary Tully
> Priority: Minor
> Labels: Failover, WARN
> Fix For: 5.10.1, 5.11.0
>
>
> 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.3.4#6332)