ActiveMQ transport connection failed: java.io.EOFException

[HN]

After configuring bamboo broker configuration settings to get the agent to work I see a continuous stream of WARNINGS (snippet below):

2018-05-22 06:21:48,009 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48058@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48058 failed: java.io.EOFException
2018-05-22 06:21:48,012 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48060@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48060 failed: java.io.EOFException
2018-05-22 06:21:48,012 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48062@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48062 failed: java.io.EOFException
2018-05-22 06:21:48,201 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48064@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48064 failed: java.io.EOFException
2018-05-22 06:21:48,202 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48066@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48066 failed: java.io.EOFException
2018-05-22 06:21:48,202 WARN [ActiveMQ Transport: tcp:///10.233.104.10:48068@54663] [Transport] Transport Connection to: tcp://10.233.104.10:48068 failed: java.io.EOFException

The IP seen above is our Reverse Proxy server. Any idea what this is and how to deal with it?

[Anonymous Coward]

Simon says:

" From the output it seems like yout reverse proxy is tearing down connections between the remote agents and Bamboo.

Please try bypassing the proxy for the TCP connections initiated by the agent to Bamboo server TCP port 54663 and verify that the remote agents can connect correctly.

If you cannot work without a reverse proxy then configure the reverse proxy to forward TCP connections coming from remote agents destined for the Bamboo server TCP port 54663.

"

Simon out.

[Chris Flynn]

@HN did you ever fix this issue?