Looks like something else tried to connect to ActiveMQ and then dropped. Do your load balancer machines have some sort of ping that it sends out?
On Fri, Jan 4, 2013 at 3:58 AM, jliezers <john.liez...@metoffice.gov.uk>wrote: > Hi, > > We're running ActiveMQ version 5.6.0 in a MASTER/SLAVE configuration on > linux. > > ActiveMQ is started via a wrapper. > > Everything appears to work but the log file reports the following at 10 > second intervals > > INFO | jvm 1 | 2013/01/03 17:29:56 | 16563455 [ActiveMQ Transport: > tcp:///x.x.x.251:30883] WARN > org.apache.activemq.broker.TransportConnection.Transpor > t - Transport Connection to: tcp://x.x.x.251:30883 failed: > java.io.EOFException > > INFO | jvm 1 | 2013/01/03 17:29:56 | 16563455 [ActiveMQ Transport: > tcp:///x.x.x.252:30883] WARN > org.apache.activemq.broker.TransportConnection.Transpor > t - Transport Connection to: tcp://x.x.x.252:30883 failed: > java.io.EOFException > > The two IP addresses in question (x.x.x.251 and x.x.x.252) are load > balancers not the host ip address of the ActiveMQ Master or Slave. > > Can anyone explain why the JVM is attempting to connect to these IPs at > all? > > Thanks > > John > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Transport-Connection-EOFException-tp4661326.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
