Hi Rainer,
now I got it what you mean about the steady state.
Thx Ingo
Rainer Jung schrieb:
Hi Ingo,
Ingo Düppe wrote:
Am I'm right, that with the following setting a reply_timeout is
detected when the tomcat doesn't reply within 10 seconds and it will
be set into error if more than 15 timeou
Hi Ingo,
Ingo Düppe wrote:
Am I'm right, that with the following setting a reply_timeout is
detected when the tomcat doesn't reply within 10 seconds and it will be
set into error if more than 15 timeouts in a minutes are detected?
worker.plexus.reply_timeout=1
Yes. The timeout gets rese
to client aborted or client
network problems
[info] jk_ajp_common.c (1996): (plexus12) request failed, because of
client write error without recovery in send loop attempt=0
[info] jk_lb_worker.c (1092): unrecoverable error 200, request
failed. Client failed in the middle of request, we can
error without recovery in send loop attempt=0
[info] jk_lb_worker.c (1092): unrecoverable error 200, request failed.
Client failed in the middle of request, we can't recover to another
instance.
[info] mod_jk.c (2270): Aborting connection for worker=plexus
First I thought, this is caused be
send loop attempt=0
[info] jk_lb_worker.c (1092): unrecoverable error 200, request failed.
Client failed in the middle of request, we can't recover to another
instance.
[info] mod_jk.c (2270): Aborting connection for worker=plexus
First I thought, this is caused because of some related ne