hi all
I saw several posts regarding the async exception (listed below) in logs
with ActiveMQ 5.0.0. We are also seeing this exception randomly in the logs,
the bad part is it breaks the connection between Broker and the client even
tho the broker is up and running and there are no network connection issues
between the broker and the client.
I got the impression from the other posts regarding this issue that this has
been fixed in 5.1 release? Can someone confirm this? This is a production
problem for us right now and would really appreciate if someone can provide
a timely response. We are setting the wireFormat.maxInactivityDuration=-1 to
in the connect url and are using durable subscribers.
*WARN 13:50:24.571,ActiveMQ Transport:
,(org.apache.activemq.ActiveMQConnection:1653)> Async exception with no
exception listener: java.io.EOFException
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)
at java.lang.Thread.run(Thread.java:619)
thanks!
jaya
--
View this message in context:
http://www.nabble.com/Async-exception-with-no-exception-listener%3A-java.io.EOFException-tp17874356p17874356.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
