No idea, it really looks like there's a communication problem to the
backend. Starting with 01:14:22 all connections that are created new are
able to send a request, but do not receive any response.
I think I would first enable Cpin/Cpong and maybe some other timeouts,
to make the communicatio
Hello Rainer,
I've let it log with debug log level all night and I managed to get what
you needed (some [error] lines).
I have the sample at http://www.craiova.ro/mod_jk.log
Cheers,
Andrei Neagoe
Rainer Jung wrote:
OK: you started with an error log entry referring to errno 104 as your
ori
OK: you started with an error log entry referring to errno 104 as your
original problem. I had the impression, you can easily reproduce this
problem. In the logs you presented - even in the full log download -
this problem is not present.
The lines you referred to below are normal. They only t
Yes, they are. It was my mistake referring to it as an error. I was
talking about:
[Sun Aug 12 22:38:53 2007] [22781:3079018176] [debug]
ajp_get_endpoint::jk_ajp_common.c (2498): acquired connection pool slot=0
[Sun Aug 12 22:38:53 2007] [22781:3079018176] [debug]
ajp_marshal_into_msgb::jk_ajp
Andrei Neagoe wrote:
I've archived a portion of the log containing 2 instances of the error.
You can download it at http://www.craiova.ro/mod_jk.log.bz2
I've tried sending it via mail but there's a limit on mail size.
I downloaded this file, uncompressed and untarred. The resulting log
file w
I've archived a portion of the log containing 2 instances of the error.
You can download it at http://www.craiova.ro/mod_jk.log.bz2
I've tried sending it via mail but there's a limit on mail size.
Thanks,
Andrei Neagoe
Rainer Jung wrote:
Your log excerpt stops exactly, when it's getting int
Your log excerpt stops exactly, when it's getting interesting.
mod_jk connects and starts to send the request, no error until that point...
We would like to check, at what point in the communication the problems
appears, and what happened immediately before etc.
Andrei Neagoe wrote:
Thanks fo
Thanks for your reply.
I've tried looking around in jetty logs (also in webapps logs) but
nothing related to the errors in mod_jk.
Also I've tried to increase the log level... and I did not find anything
(from my point of view):
[Sun Aug 12 22:15:49 2007] [22077:3079018176] [debug]
map_uri_to
No idea, what's happening, but if you can reproduce very easily, then
you could increase the jk log level to debug or even trace. That way we
will see more precisely, at what point the communication breaks.
You error code 104 on many platforms is "Connection reset by peer". So
there might be a
Hello,
Until a recent upgrade I've been using Apache2 with Jetty and mod_jk2
just fine. Now, after I upgraded Apache to 2.2.3 and switched to mod_jk
1.2.18 and having the same version of Jetty (4.2.24) I find the
following in the mod_jk.log:
[Sun Aug 12 15:53:13 2007] [9685:3078895296] [erro
10 matches
Mail list logo
