CODEWITHSUNDEEP
javasslactivemq-classiceofexception
Satscreate
Satscreate

Reputation: 535

java.io.EOFException - ActiveMQ messaging broker

Here is the trace which is from startup.log (tomcat)

java.io.EOFException
        at java.io.DataInputStream.readInt(DataInputStream.java:392)
        at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
        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.lang.Thread.run(Thread.java:745)

Using below URL to connect broker:

failover:(ssl://{0}?wireFormat.maxInactivityDuration=0)?maxReconnectAttempts=5

{0} - actual ip address to connect

Added the maxinactivity =0 because of below WARN, but getting this exception in log 5 times a day.

org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:52659

whats wrong with my configurations? or should i investigate further in ssl or tcp connection transport layers? what is the reason behind the exception?

Upvotes: 2

Views: 4473

Answers (1)

Tim Bish
Tim Bish

Reputation: 18356

The errors indicate that something is happening at the socket level that is causing a disconnect or half open socket to result and therefore the client is detect and reporting that it has disconnected.

There are many reasons why this could be happening, you might have a load balancer in the middle that is killing the client connection or the broker might be getting hung etc. It doesn't appear to be a client issue, the client is telling you the connection failed.

Upvotes: 1

Related Questions