gjae Chang
From: Igor Cicimov
Reply-To:
Date: Friday, May 25, 2012 7:32 AM
To:
Subject: Re: [users@httpd] CLOSE_WAIT problem
You can reduce the time on OS level if you want by tuning the tcp stack.
On May 25, 2012 3:00 AM, "Bongjae Chang" wrote:
> Hi Eric,
> Thank you for q
You can reduce the time on OS level if you want by tuning the tcp stack.
On May 25, 2012 3:00 AM, "Bongjae Chang" wrote:
> Hi Eric,
> Thank you for quick reply.
>
> You mean if Apache picks up the closed conn and tries to do some I/O
> operations like writing, Apache will failover the conn(with
Hi Eric,
Thank you for quick reply.
You mean if Apache picks up the closed conn and tries to do some I/O
operations like writing, Apache will failover the conn(with closing the
conn and creating/reusing new conn). So CLOSE_WAIT may be normal in this
case, right?
IMHO, as soon as connections are c
Backend connections sit in close_wait until Apache tries to reuse
them. What problem does it cause?
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Hi all,
I sent this issue to the dev mailing but I couldn't receive any responses. I
think this subject is fit to be discussed in the user mailing so I am
sending this again. :-)
When I tested mod_proxy + mod_proxy_balancer + (mod_proxy_ajp or
mod_proxy_http) with worker mpm, I always met CLOSE_W