httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Oliver <acoli...@gmail.com>
Subject Re: CLOSE_WAIT problem
Date Fri, 25 May 2012 16:09:44 GMT
You need to specify a pool size.  Also ask on the users list.

Thanks,

Andrew C. Oliver

On Fri, May 25, 2012 at 5:21 AM, Bongjae Chang <bongjae.chang@gmail.com> wrote:
> Hi Reindl,
>
> Thank you for the link.
>
> When I read the link, it also said "Faulty scenarios would be like
> filedescriptor leak, server not being
> execute close() on socket leading to pile up of close_wait sockets".
>
> I raised the very same issue(mod_proxy's backend connection which has been
> already closed).
>
> Thanks!
>
> Regards,
> Bongjae Chang
>
>
>
>
> On 5/25/12 6:01 PM, "Reindl Harald" <h.reindl@thelounge.net> wrote:
>
>>
>>
>>Am 25.05.2012 10:52, schrieb Bongjae Chang:
>>>>> Is the watcher thread which is going through all of the connections
>>>>> looking to see if they have been closed by the peer only solution?
>>>>
>>>> There is no thread.
>>>
>>> I see.. then I think that it will be useful if mod_proxy will support
>>>the
>>> feature later(just my opinion).
>>
>>as far as i understand this is normal TCP behavior for reusing sockets
>>
>>http://blogs.technet.com/b/janelewis/archive/2010/03/09/explaining-close-w
>>ait.aspx
>>
>
>

Mime
View raw message