You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "H B (JIRA)" <ji...@apache.org> on 2008/01/06 01:15:43 UTC
[jira] Created: (AMQ-1538) EOFException on idling listener
EOFException on idling listener
-------------------------------
Key: AMQ-1538
URL: https://issues.apache.org/activemq/browse/AMQ-1538
Project: ActiveMQ
Issue Type: Bug
Components: JMS client
Affects Versions: 5.0.0
Environment: JDK 1.6, Windows Vista
Reporter: H B
Ever since I switched over to 5.0.0, I got these EOFException in the onException() callback of the listener when it is sitting idle. I also notice that similar exception is thrown in the MQ broker, especially after Windows wakes up from idling.
This does not happen in 4.1.
Is this a bug in 5.0?
thx
----
ERROR Server [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616|] JMS connection received asynchronous exception
javax.jms.JMSException: java.io.EOFException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1642)
at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1659)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:169)
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:95)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:176)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
... 1 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1538) EOFException on idling listener
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1538:
-------------------------------
Assignee: Rob Davies
> EOFException on idling listener
> -------------------------------
>
> Key: AMQ-1538
> URL: https://issues.apache.org/activemq/browse/AMQ-1538
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.0.0
> Environment: JDK 1.6, Windows Vista
> Reporter: H B
> Assignee: Rob Davies
>
> Ever since I switched over to 5.0.0, I got these EOFException in the onException() callback of the listener when it is sitting idle. I also notice that similar exception is thrown in the MQ broker, especially after Windows wakes up from idling.
> This does not happen in 4.1.
> Is this a bug in 5.0?
> thx
> ----
> ERROR Server [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616|] JMS connection received asynchronous exception
> javax.jms.JMSException: java.io.EOFException
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1642)
> at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1659)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
> at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:169)
> at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:95)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:176)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
> at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> ... 1 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1538) EOFException on idling listener
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1538.
-----------------------------
Fix Version/s: 5.1.0
Resolution: Fixed
> EOFException on idling listener
> -------------------------------
>
> Key: AMQ-1538
> URL: https://issues.apache.org/activemq/browse/AMQ-1538
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.0.0
> Environment: JDK 1.6, Windows Vista
> Reporter: H B
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> Ever since I switched over to 5.0.0, I got these EOFException in the onException() callback of the listener when it is sitting idle. I also notice that similar exception is thrown in the MQ broker, especially after Windows wakes up from idling.
> This does not happen in 4.1.
> Is this a bug in 5.0?
> thx
> ----
> ERROR Server [AcitveMQ Connection Worker: tcp://localhost/127.0.0.1:61616|] JMS connection received asynchronous exception
> javax.jms.JMSException: java.io.EOFException
> at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1642)
> at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1659)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:98)
> at org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
> at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:169)
> at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:95)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:176)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
> at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
> at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
> at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> ... 1 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.