EOFExceptions and Broken Pipe exceptions everywhere in 5.0 (my services seem to
run fine under 4.1 and 4.1.1 and somewhat better in 5.1-SNAPSHOT [if you don't
count the queue size problem] which is critical)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AMQ-1603
URL: https://issues.apache.org/activemq/browse/AMQ-1603
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.0.0
Reporter: Denis Abramov
Priority: Blocker
I keep getting these errors when any of my services startup... This version
doesn't look too stable.
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:595)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:358)
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
and this one:
javax.jms.JMSException: Channel was inactive for too long:
puccell/10.0.55.197:61616
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.InactivityMonitor$4.run(InactivityMonitor.java:108)
Caused by: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long: puccell/10.0.55.197:61616
... 1 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
