activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Transport failed, attempting to automatically reconnect due to: java.io.EOFException
Date Mon, 05 Mar 2007 15:25:39 GMT
On 3/5/07, Jamie McCrindle <jamiemccrindle@gmail.com> wrote:
> Hi all,
>
> I keep getting the following exception at what appear to be random intervals:
>
> 2007-03-05 14:42:40,367 INFO [ActiveMQ Transport: tcp://localhost/1
> 27.0.0.1:51515] FailoverTransport.handleTransportFailure | Transport failed, att
> empting to automatically reconnect due to: java.io.EOFException
> java.io.EOFException
>         at java.io.DataInputStream.readInt(DataInputStream.java:358)
>         at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.
> java:267)
>         at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo
> rt.java:156)
>         at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
> 136)
>         at java.lang.Thread.run(Thread.java:595)
>
> Any ideas? It doesn't appear to be affecting the messaging...
>
> I'm using:
>
> ActiveMQ 4.1.0 and a broker url of: tcp://localhost:61616
>
> activemq.conf is the standard one out of the 4.1 distro.

It typically just means that the socket has closed while the async
reading thread is trying to read from the socket. It can generally be
ignored. If you were using a URL of failover:tcp://localhost:61616
then the transport would automatically reconnect under the covers for
you. If you're not using failover then maybe you're closing
connections?

-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message