Do you know what that IP is?
We have similar messages for multiple services that result in an admin
setting up port monitor (nagios, etc.) without the protocol specifics.
Similar messages typically show up when the service is being used by a
client that does not support the protocol, and instead abruptly closes the
connection. These might be network monitoring tools, but may also point to
a incompletely configured client, that attempts to connect to the AMQ with
the wrong protocol, or at the wrong port.
На пн, 30.09.2019 г. в 15:49 ч. Jose Manuel Vega Monroy <
[hidden email]> написа:
Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException
I second JB there; if the broker was hitting a limit to the number of
connections it could accept, there wouldn't be errors in the broker's logs
about how the client closed the connection unexpectedly.
On Sun, Oct 6, 2019 at 5:24 AM Jean-Baptiste Onofré <[hidden email]> wrote: