You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Jose Manuel Vega Monroy <jo...@williamhill.com> on 2019/09/30 12:49:28 UTC

Transport Connection - java.io.EOFException

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 failed: java.io.EOFException

Any idea what’s the problem?

Our Apache ActiveMq version is 5.15.0.

Thanks

[https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180]<http://www.williamhill.com/>
[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: jose.monroy@williamhill.com<ma...@williamhill.com>
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA




Re: Transport Connection - java.io.EOFException

Posted by Tim Bain <tb...@alumni.duke.edu>.
Load balancer health checks are another possible source of connections that
close without completing a protocol handshake.

Tim

On Wed, Oct 2, 2019, 1:27 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi,
>
> Don't you have a disconnect from clients ?
>
> Are you using failover or directly the transport ?
>
> Regards
> JB
>
> On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
> > 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 failed:
> > java.io.EOFException***
> >
> >
> >
> > Any idea what’s the problem?
> >
> >
> >
> > Our Apache ActiveMq version is *5.15.0*.
> >
> >
> >
> > Thanks
> >
> >
> >
> > https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180
> > <http://www.williamhill.com/>
> >
> > 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: jose.monroy@williamhill.com <ma...@williamhill.com>
> >
> > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
> >
> >
> >
> >
> >
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException

Posted by Tim Bain <tb...@alumni.duke.edu>.
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.

Tim

On Sun, Oct 6, 2019 at 5:24 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi Jose,
>
> I don't think it's because your reach the max connection on the
> transport connector side.
>
> I'm more suspecting the connection factory on client side. Are you using
> poolable connection factory ?
>
> What ActiveMQ version are you using for both client and broker ?
>
> Regards
> JB
>
> On 06/10/2019 09:56, Jose Manuel Vega Monroy wrote:
> > Hi there,
> >
> > It could be one client continuously trying to connect, but maybe was
> reached limit of possible connections in broker side?
> >
> > Thanks
> >
> > Get Outlook for Android<https://aka.ms/ghei36>
> > ________________________________
> > From: Jose Manuel Vega Monroy <jo...@williamhill.com>
> > Sent: Thursday, October 3, 2019 12:18:17 PM
> > To: Luca Segafredo <Lu...@williamhill.com>; Cezary Gajdzinski <
> Cezary.Gajdzinski@williamhill.com>; Andreea Nicula <
> andreea.nicula@williamhill.com>; Laur Aliste <la...@williamhill.com>
> > Subject: Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException
> >
> > FYI
> >
> >
> >  <http://www.williamhill.com/>
> >  <http://www.whenthefunstops.co.uk/>
> > Jose Manuel Vega Monroy
> > Java Developer / Software Developer Engineer in Test
> > Direct: +0035 0 2008038 (Ext. 8038)
> > Email: jose.monroy@williamhill.com
> > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
> >
> >
> >
> >
> > On 02/10/2019, 09:27, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
> >
> >     Hi,
> >
> >     Don't you have a disconnect from clients ?
> >
> >     Are you using failover or directly the transport ?
> >
> >     Regards
> >     JB
> >
> >     On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
> >     > 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 failed:
> >     > java.io.EOFException***
> >     >
> >     >
> >     >
> >     > Any idea what’s the problem?
> >     >
> >     >
> >     >
> >     > Our Apache ActiveMq version is *5.15.0*.
> >     >
> >     >
> >     >
> >     > Thanks
> >     >
> >     >
> >     >
> >     >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_WHlogo.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=BF-abs61nxm5JY4H1aGTSDXiMcALDfOysU5HlRb-vyI&e=
> >     > <http://www.williamhill.com/>
> >     >
> >     >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_senet.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=kPY3sb8CqVUTPpLnnhDvDzr86Hpg6utGefzibNiZ5lU&e=
> >     > <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.whenthefunstops.co.uk_&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=dRKX8A7Nspjrg4cXOQp07whNpqXmVqpMc7P4SV-ztao&e=
> >
> >     >
> >     >
> >     >
> >     > *Jose Manuel Vega Monroy **
> >     > **Java Developer / Software Developer Engineer in Test*
> >     >
> >     > Direct: +*0035 0 2008038 (Ext. 8038)*
> >     > Email: jose.monroy@williamhill.com <mailto:
> jose.monroy@williamhill.com>
> >     >
> >     > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >
> >     --
> >     Jean-Baptiste Onofré
> >     jbonofre@apache.org
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.nanthrax.net&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=VLLwaDvJqGrR22m1i9gXVsyAMnAwd7cTVh8hTZtYWmI&e=
> >     Talend -
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.talend.com&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=Hpq8nbWqHiT_Q5oOMUNsI6XZtoXRP8aidCK-KEakFmw&e=
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jose,

I don't think it's because your reach the max connection on the
transport connector side.

I'm more suspecting the connection factory on client side. Are you using
poolable connection factory ?

What ActiveMQ version are you using for both client and broker ?

Regards
JB

On 06/10/2019 09:56, Jose Manuel Vega Monroy wrote:
> Hi there,
> 
> It could be one client continuously trying to connect, but maybe was reached limit of possible connections in broker side?
> 
> Thanks
> 
> Get Outlook for Android<https://aka.ms/ghei36>
> ________________________________
> From: Jose Manuel Vega Monroy <jo...@williamhill.com>
> Sent: Thursday, October 3, 2019 12:18:17 PM
> To: Luca Segafredo <Lu...@williamhill.com>; Cezary Gajdzinski <Ce...@williamhill.com>; Andreea Nicula <an...@williamhill.com>; Laur Aliste <la...@williamhill.com>
> Subject: Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException
> 
> FYI
> 
> 
>  <http://www.williamhill.com/>
>  <http://www.whenthefunstops.co.uk/>
> Jose Manuel Vega Monroy
> Java Developer / Software Developer Engineer in Test
> Direct: +0035 0 2008038 (Ext. 8038)
> Email: jose.monroy@williamhill.com
> William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
> 
> 
> 
> 
> On 02/10/2019, 09:27, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:
> 
>     Hi,
> 
>     Don't you have a disconnect from clients ?
> 
>     Are you using failover or directly the transport ?
> 
>     Regards
>     JB
> 
>     On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
>     > 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 failed:
>     > java.io.EOFException***
>     >
>     >
>     >
>     > Any idea what’s the problem?
>     >
>     >
>     >
>     > Our Apache ActiveMq version is *5.15.0*.
>     >
>     >
>     >
>     > Thanks
>     >
>     >
>     >
>     > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_WHlogo.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=BF-abs61nxm5JY4H1aGTSDXiMcALDfOysU5HlRb-vyI&e=
>     > <http://www.williamhill.com/>
>     >
>     > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_senet.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=kPY3sb8CqVUTPpLnnhDvDzr86Hpg6utGefzibNiZ5lU&e=
>     > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.whenthefunstops.co.uk_&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=dRKX8A7Nspjrg4cXOQp07whNpqXmVqpMc7P4SV-ztao&e= >
>     >
>     >
>     >
>     > *Jose Manuel Vega Monroy **
>     > **Java Developer / Software Developer Engineer in Test*
>     >
>     > Direct: +*0035 0 2008038 (Ext. 8038)*
>     > Email: jose.monroy@williamhill.com <ma...@williamhill.com>
>     >
>     > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
>     >
>     >
>     >
>     >
>     >
>     >
>     >
> 
>     --
>     Jean-Baptiste Onofré
>     jbonofre@apache.org
>     https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.nanthrax.net&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=VLLwaDvJqGrR22m1i9gXVsyAMnAwd7cTVh8hTZtYWmI&e=
>     Talend - https://urldefense.proofpoint.com/v2/url?u=http-3A__www.talend.com&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=Hpq8nbWqHiT_Q5oOMUNsI6XZtoXRP8aidCK-KEakFmw&e=
> 
> 

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException

Posted by Jose Manuel Vega Monroy <jo...@williamhill.com>.
Hi there,

It could be one client continuously trying to connect, but maybe was reached limit of possible connections in broker side?

Thanks

Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Jose Manuel Vega Monroy <jo...@williamhill.com>
Sent: Thursday, October 3, 2019 12:18:17 PM
To: Luca Segafredo <Lu...@williamhill.com>; Cezary Gajdzinski <Ce...@williamhill.com>; Andreea Nicula <an...@williamhill.com>; Laur Aliste <la...@williamhill.com>
Subject: Re: [EXTERNAL] Re: Transport Connection - java.io.EOFException

FYI


 <http://www.williamhill.com/>
 <http://www.whenthefunstops.co.uk/>
Jose Manuel Vega Monroy
Java Developer / Software Developer Engineer in Test
Direct: +0035 0 2008038 (Ext. 8038)
Email: jose.monroy@williamhill.com
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA




On 02/10/2019, 09:27, "Jean-Baptiste Onofré" <jb...@nanthrax.net> wrote:

    Hi,

    Don't you have a disconnect from clients ?

    Are you using failover or directly the transport ?

    Regards
    JB

    On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
    > 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 failed:
    > java.io.EOFException***
    >
    >
    >
    > Any idea what’s the problem?
    >
    >
    >
    > Our Apache ActiveMq version is *5.15.0*.
    >
    >
    >
    > Thanks
    >
    >
    >
    > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_WHlogo.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=BF-abs61nxm5JY4H1aGTSDXiMcALDfOysU5HlRb-vyI&e=
    > <http://www.williamhill.com/>
    >
    > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.williamhillplc.com_content_signature_senet.gif-3Fwidth-3D180&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=kPY3sb8CqVUTPpLnnhDvDzr86Hpg6utGefzibNiZ5lU&e=
    > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.whenthefunstops.co.uk_&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=dRKX8A7Nspjrg4cXOQp07whNpqXmVqpMc7P4SV-ztao&e= >
    >
    >
    >
    > *Jose Manuel Vega Monroy **
    > **Java Developer / Software Developer Engineer in Test*
    >
    > Direct: +*0035 0 2008038 (Ext. 8038)*
    > Email: jose.monroy@williamhill.com <ma...@williamhill.com>
    >
    > William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
    >
    >
    >
    >
    >
    >
    >

    --
    Jean-Baptiste Onofré
    jbonofre@apache.org
    https://urldefense.proofpoint.com/v2/url?u=http-3A__blog.nanthrax.net&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=VLLwaDvJqGrR22m1i9gXVsyAMnAwd7cTVh8hTZtYWmI&e=
    Talend - https://urldefense.proofpoint.com/v2/url?u=http-3A__www.talend.com&d=DwIDaQ&c=pWn2jKJ-j-AhxLuiRFe-Qw&r=i5Pk4pirVCmwsmddZqplM1jyQtVWeoOOb-vkuqku5P8&m=Zt2Fhl0gn_-6_Bs-66hN7o6Kjt7ylNKEpnzD0koyFRM&s=Hpq8nbWqHiT_Q5oOMUNsI6XZtoXRP8aidCK-KEakFmw&e=



Re: Transport Connection - java.io.EOFException

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

Don't you have a disconnect from clients ?

Are you using failover or directly the transport ?

Regards
JB

On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
> 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 failed:
> java.io.EOFException***
> 
>  
> 
> Any idea what’s the problem?
> 
>  
> 
> Our Apache ActiveMq version is *5.15.0*.
> 
>  
> 
> Thanks
> 
>  
> 
> https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180
> <http://www.williamhill.com/>
> 
> 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: jose.monroy@williamhill.com <ma...@williamhill.com>
> 
> William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
> 
>  
> 
>  
> 
>  
> 

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Transport Connection - java.io.EOFException

Posted by Lachezar Dobrev <l....@gmail.com>.
  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 <
jose.monroy@williamhill.com> написа:

> 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: jose.monroy@williamhill.com
>
> William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
>
>
>
>
>
>
>