You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@ws.apache.org by Craig Kelley <ck...@ibnads.com> on 2003/06/18 20:20:33 UTC

CLOSE_WAIT

Hello everyone;

Sorry if this question has been asked before, but I couldn't find a way
to search through the archives of this list.  We are using v1.1 and are
seeing situations in which the Webserver object freezes with a whole
bunch of CLOSE_WAIT socket states.  No exceptions are thrown, however,
which seems strange if it had run out of runnable objects.  We are using
Java 1.4.1 under Linux (redhat 7.3), and are considering the idea of
setting SO_LINGER socket options via Socket's setSoLinger method, but we
wanted to check if anyone else has seen this sort of behavior before we
do so.

TIA,

  Craig

-- 
Craig Kelley <ck...@ibnads.com>
In-Store Broadcasting Network


Re: CLOSE_WAIT

Posted by "Dan K." <da...@yorku.ca>.
Hi Craig,

FWIW...
Not here.  We also use xml-rpc v1.1 and the included WebServer in a
customized xml-rpc server which we've deployed with serveral instances and
none exhibit this behaviour.  We use java 1.4.1 on debian linux (woody).

Regards,
Dan

On Wed, 18 Jun 2003, Craig Kelley wrote:

>
> Hello everyone;
>
> Sorry if this question has been asked before, but I couldn't find a way
> to search through the archives of this list.  We are using v1.1 and are
> seeing situations in which the Webserver object freezes with a whole
> bunch of CLOSE_WAIT socket states.  No exceptions are thrown, however,
> which seems strange if it had run out of runnable objects.  We are using
> Java 1.4.1 under Linux (redhat 7.3), and are considering the idea of
> setting SO_LINGER socket options via Socket's setSoLinger method, but we
> wanted to check if anyone else has seen this sort of behavior before we
> do so.
>
> TIA,
>
>   Craig
>
> --
> Craig Kelley <ck...@ibnads.com>
> In-Store Broadcasting Network
>