Hi- This error looks to be caused by zero bytes being sent across the wire, which is unexpected and leads to the EOFException to be thrown and then logged at a WARN level on the broker-side.
Does your broker have a load balancer, health check or security scanner running against the ActiveMQ broker port? These tools would make a connection and not send any data across, which could lead to this scenario. Thanks, Matt Pavlovich > On Oct 21, 2024, at 5:22 AM, rop <rop...@gmail.com> wrote: > > We are running an application using ActiveMQ (currently, version 5.18.3) > with multiple queues and listeners since several years. > Has worked fine, so far --- only, in the last week > we are sometimes seeing Warnings like this in the log-files: > > 2024-10-18 14:23:07,844 [ActiveMQ Transport: > tcp:///127.0.0.1:61616@44966][FailoverTransport:283] > WARN org.apache.activemq.transport.failover.FailoverTransport - Transport > (tcp://127.0.0.1:61616) failed, not attempting to automatically reconnect > java.io.EOFException: null > at > java.base/java.io.DataInputStream.readFully(DataInputStream.java:210) > at > java.base/java.io.DataInputStream.readInt(DataInputStream.java:385) > at > org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:280) > at > org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:240) > at > org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:232) > at > org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) > at java.base/java.lang.Thread.run(Thread.java:1583) > > Evertyhing still seems to work fine without issues. > I'm just a bit concerned what is causing these warnings? > > Anyone can explain what's going on? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
