Try disabling or increasing the inactivity timeout on the brokers' corresponding transport connector element. For example this will disable the inactivity monitor.
<transportConnector name="openwire" uri="tcp://localhost:61616?wireFormat.maxInactivityDuration=0"/> Joe Goto www.ttmsolutions.com for a free ActiveMQ user guide /U wrote: > > I am connecting two external brokers as follows: > > <transportConnector name="openwire" uri="tcp://localhost:61616" > /> > <networkConnectors> > <networkConnector name="other-broker" > uri="static://(tcp://10.1.1.135:61616)" > /> > </networkConnectors> > > Periodically, the connection breaks with the following message; when this > happens, the > messaging between the two brokers is aborted. I've read on some forums > that due to this > issue alone some have stopped using 5.0.0. Is there a simple solution to > this > (in my configuration) or should I stop using 5.0? > > Thanks for any suggestions! > > /Ur > > > [ActiveMQ Transport: tcp:///10.1.1.134:61616] 2008-03-15 21:53:20,786 > [WARN ,FailoverTransport 236] Transport failed, attempting to > automatically reconnect due to: 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) > > > > -- View this message in context: http://www.nabble.com/AMQ5.0.0%3A-%22Transport-failed%2C-attempting-to-automatically-reconnect-due-to%3A-java.io.EOFException%22-tp16076047s2354p16092845.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
