I don't think there is enough information here to really solve the issue. The EOFException just means that the clients have been disconnected but it doesn't say why. It could be a number of reasons including network issues causing the disconnect or exceptions on message receive, etc. Can you try turning up the logging to debug to see if any more useful information shows up in the logs?
On Fri, Jul 3, 2015 at 1:56 AM, Cadmean <hzcadm...@hotmail.com> wrote: > I have built a broker network with 4 brokers and 5000 clinets. ( I have > changed the max connection of each broker to 2500 in activemq.xml). Every > broker using failover forever to build the connection. > The problem is, after a uncertain time, some clients (about 20 clients > which > OS incluing AIX and Suse Linux) start to show the following logs and keep > trying to reconnect the broker. Also, I can see those clients keep getting > online and offline when listening to the system topic > TOPIC://ActiveMQ.Advisory.Connetion. > > [2015-06-10 09:05:51,412 [WARN][ActiveMQ Transport: > tcp://83.28.33.224:61616@47664]--Transport (tcp://83.28.33.224:61616 > @47664) > failed, reason: , attempting to automatically reconnect > java.io.EOFException > at java.io.DataInputStream.readInt(DataInputStream.java:386) > at org.apache.activemq.openwire.OpenWireFormat.unmarshal > (OpenWireFOrmat.java:258) > at org.apache.activemq.transport.tcp.TcpTransport.readCommand > (TcpTransport.java:221) > at org.apache.activemq.transport.tcp.TcpTransport.doRun > (TcpTransport.java:213) > at org.apache.activemq.transport.tcp.TcpTransport.run > (TcpTransport.java:196) > at java.lang.Thread.run(Thread.java:735) > > Enviroment: > Suse Linux 11 sp2,JDK 1.7 > the jvm memory is set to 2G > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Transport-failed-please-helpT-T-tp4698539.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
