tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Lynch <>
Subject Modjk surfacing errno 115
Date Fri, 04 Mar 2016 19:35:10 GMT
Hi there,

We have a very heavily used implementation of modjk 1.2.35 running in
Apache 2.2.15 i686 on CentOS 6.7 x86_64. After Apache startup, our system
will perform optimally with no errors for about 24 hours, after which we
begin to see this message:

connecting to backend failed. Tomcat is probably not started or is
listening on the wrong port (errno=115)

Once we start seeing this error for one backend/worker, we begin seeing the
same errors for eventually all workers. This problem doesn't go away until
we restart Apache. Our setup consists of 720 workers per apache, with
multiple apache servers, and each apache server also has several other
sites configured with modjk serving other tomcat backends. It should be
noted that we do not see the same error with other sites, nor do we have so
many workers defined for any other site.

We've searched through past mailings to try and find the same issue. The
couple times we saw it brought up the error code 110 was also mentioned. It
should be noted we do not see the same pattern. errno 110 does show but
outside of the window when the problem begins and is at its worst. We
believe this issue is not configuration related.

We're posting this here to try and gather more data. Our process prohibits
an upgrade of any kind without plenty of evidence supporting our position.
Hoping that some individuals might have seen this particular issue, or if
there is any data on whether this could be a bug. Hopefully we're correct
in thinking this issue is not a configuration problem, but we'll help to
rule out.


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