tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Bossu <pbo...@gmail.com>
Subject Re: mod_jk errors errno=110 and errno=115
Date Sun, 21 Apr 2013 19:57:52 GMT
Thank you Rainer, it was very helpful.
Sorry for late answer.

On Sun, Feb 17, 2013 at 12:02 PM, Rainer Jung <rainer.jung@kippdata.de>wrote:

> On 14.02.2013 14:17, Philippe Bossu wrote:
> > We have a mod_jk in version 1.2.28 with Apache 2.16  fronting a Tomcat
> > server in version 6 on JDK6.
> >
> > We are facing long response times and timeouts from time to time.
> > Mod_jk log files show the following errors:
> >
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_connect_to_endpoint::jk_ajp_common.c
> > (1035): (nodeXX) cping/cpong after connecting to the backend server
> failed
> > (errno=110)
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_send_request::jk_ajp_common.c (1630):
> > (nodeXX) connecting to backend failed. Tomcat is probably not started or
> is
> > listening on the wrong port (errno=110)
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_connect_to_endpoint::jk_ajp_common.c
> > (1035): (nodeXX) cping/cpong after connecting to the backend server
> failed
> > (errno=110)
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_send_request::jk_ajp_common.c (1630):
> > (nodeXX) connecting to backend failed. Tomcat is probably not started or
> is
> > listening on the wrong port (errno=110)
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_service::jk_ajp_common.c (2626):
> (nodeXX)
> > connecting to tomcat failed.
> >
> >
> > [XXXXXXXX][XXXXXXXXX] [error] ajp_send_request::jk_ajp_common.c (1630):
> > (nodeYY) connecting to backend failed. Tomcat is probably not started or
> is
> > listening on the wrong port (errno=115)
> >
> > [XXXXXXXX][XXXXXXXXX] ] [error] ajp_send_request::jk_ajp_common.c (1630):
> > (nodeYY) connecting to backend failed. Tomcat is probably not started or
> is
> > listening on the wrong port (errno=115)
> > [XXXXXXXX][XXXXXXXXX]  [error] ajp_service::jk_ajp_common.c (2626):
> > (nodeYY) connecting to tomcat failed.
> >
> >
> > What could be the explanations except for Tomcat Thread pool not having
> > threads available anymore ? Thing we checked.
> >
> > Was there fixes in new mod_jk versions (1.2.37) regarding issues like
> these
> > ?
>
> System errno numbers are platform dependent and you didn't tell us your
> OS. See e.g.
>
> http://www.ioplex.com/~miallen/errcmpp.html
>
> I guess oyu are on Linux and then those are expected errnos. The reason
> is not expected on the jk side of things. As you said, it can be your
> Tomcat got stuck - take Thread Dumps when this is happening to
> investigate, or there's a network problem including possibly firewalls
> in between mod_jk and Tomcat.
>
> Regards,
>
> Rainer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message