Is there a way to make sure that client always disconnects properly. I dont
have any control over the client code.Its a external client but I can change
settings in the broker.
Thanks
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Transport-failed-java-io-
Maybe a client didn't disconnect properly?
On Wed, Jun 5, 2013 at 11:51 AM, manua wrote:
> Hi,
>
> In ActiveMQ logs, I keep on getting the following exceptions.
>
> 2013-06-05 12:37:43,886 | INFO | Transport failed:
Hi,
In ActiveMQ logs, I keep on getting the following exceptions.
2013-06-05 12:37:43,886 | INFO | Transport failed: java.io.EOFException |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: ssl:///:54978
2013-06-05 12:37:43,888 | INFO | Transport failed
-06-04 18:00:52,633 | INFO | Transport failed: java.io.EOFException |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: ssl:///:2276
2013-06-04 18:00:56,675 | INFO | Transport failed: java.io.IOException:
Unknown data type: 47
.
Doesn't look like it effects functionality, but I can't be 100% sure
Upgrading to 5.x seems to be the way to go. Thanks again
From: Bruce Snyder [bruce.sny...@gmail.com]
Sent: 29 March 2010 22:22
To: users@activemq.apache.org
Subject: Re: Transp
On Mon, Mar 29, 2010 at 3:54 PM, Cristian Botiza
wrote:
> I notice this error (logged as debug) from time to time in the AMQ logs:
>
> java.io.EOFException
> at java.io.DataInputStream.readInt(Unknown Source)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
I notice this error (logged as debug) from time to time in the AMQ logs:
java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpT