If we're receiving an error 115, could this mean that any timeout is kind
of irrelevant? The first attempt to create the socket immediately ends with
this code. 100ms later, per retry_interval, the same error is immediately
returned. The code at line 627 tests the return val from this line which
Am 05.03.2016 um 00:09 schrieb Max Lynch:
Hi Rainer, I will do my best to provide those things.
Here is what looks like the full sequence from the our log:
[46055:3512666992] [info] jk_open_socket::jk_connect.c (627): connect to
_ip_:12409 failed (errno=115)
[46055:3512666992] [info]
Hi Rainer, I will do my best to provide those things.
Here is what looks like the full sequence from the our log:
[46055:3512666992] [info] jk_open_socket::jk_connect.c (627): connect to
_ip_:12409 failed (errno=115)
[46055:3512666992] [info] ajp_connect_to_endpoint::jk_ajp_common.c (992):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max,
On 3/4/16 2:35 PM, Max Lynch wrote:
> Hi there,
>
> We have a very heavily used implementation of modjk 1.2.35 running
> in Apache 2.2.15
> We're posting this here to try and gather more data. Our process
> prohibits an upgrade of any kind
Am 04.03.2016 um 20:35 schrieb Max Lynch:
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:
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
