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 < [email protected]> написа: > Hi there, > > > > I can see a lot of log traces like this, which *around 2 seconds as > difference each one, and different port* *each time*: > > > > *2019-09-30 13:43:45,198 [ActiveMQ Transport: > tcp:///10.216.216.200:41710@61321] WARN (TransportConnection.java:237) - > Transport Connection to: tcp://10.216.216.200:41710 > <http://10.216.216.200:41710> failed: java.io.EOFException* > > > > Any idea what’s the problem? > > > > Our Apache ActiveMq version is *5.15.0*. > > > > Thanks > > > > [image: > https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180] > <http://www.williamhill.com/> > > [image: > https://www.williamhillplc.com/content/signature/senet.gif?width=180] > <http://www.whenthefunstops.co.uk/> > > *Jose Manuel Vega Monroy * > *Java Developer / Software Developer Engineer in Test* > > Direct: +*0035 0 2008038 (Ext. 8038)* > Email: [email protected] > > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA > > > > > > >
