W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1997

Re: Thread overloading

From: Mark Friedman <mark@intraspect.com>
Date: Tue, 09 Dec 1997 13:57:56 -0800
Message-ID: <348DBEE4.5CC5C327@intraspect.com>
To: www-jigsaw@w3.org, jigsaw@w3.org, ylafon@w3.org
I have a little more information on this problem. It seems that I only
have 20 socket-client threads in use even though MAXTHREADS is the
default 40. Presumably, Jigsaw should create additional threads and
shouldn't be refusing connections until it's hit MAXTHREADS (or perhaps
MAXCLIENTS, which is the default 32).

-Mark

Mark Friedman wrote:

> I'm having a terrible problem with running out of client threads, even
> after all HTTP connections have been closed by any browsers. I
> previously sent the two attached messages but have received no
> response.
> I could really use some help, please.
>
> Thanks in advace.
>
> -Mark
>
>    ----------------------------------------------------------------
>
> Subject: Re: Some Problems!
> Date: Wed, 19 Nov 1997 10:08:16 -0800
> From: Mark Friedman <mark@intraspect.com>
> Organization: Intraspect
> To: Jigsaw Mailinglist <www-jigsaw@w3.org>
> CC: jigsaw@w3.org
> References: <01bcf4ef$ff56a200$1cea1b81@kopernikus.iaik.tu-graz.ac.at>
>
> I also have a problem with refused connections due to thread
> overloading. In
> my case the server regularly grinds to a halt whereby it never accepts
> any
> more connections and all I can do is kill it and restart it.
>
> When I last described this problem the answer from the Jigsaw folks
> was that
> there was a problemin the alpha-5 Jigsaw that they knew about that
> might cause
> this problem and that that problem was fixed in beta-1. Unfortunately
> it
> doesn't seem to have fixed this problem. Can anybody help me? What
> would make
> Jigsaw connection threads stick around forever?
>
> Thanks in advance.
>
> -Mark
>
> Wolfgang Platzer wrote:
>
> ...
>
>    ----------------------------------------------------------------
>
> Subject: Re: Some Problems!
> Date: Thu, 20 Nov 1997 10:56:24 -0800
> From: Mark Friedman <mark@intraspect.com>
> Organization: Intraspect
> To: Jigsaw Mailinglist <www-jigsaw@w3.org>, jigsaw@w3.org
>
> eferences: <01bcf4ef$ff56a200$1cea1b81@kopernikus.iaik.tu-graz.ac.at> <34732B10.D1C08894@intraspect.com>
>
> I've finally been able to catch with jdb my problem with running out
> of client threads. I notice that all the socket-client threads are in
> the following state:
>
>   [1] java.net.SocketInputStream.read (SocketInputStream:92)
>   [2] java.io.BufferedInputStream.fill (BufferedInputStream:135)
>   [3] java.io.BufferedInputStream.read (BufferedInputStream:162)
>   [4] w3c.www.mime.MimeParser.parse (pc 16)
>   [5] w3c.jigsaw.http.Client.getNextRequest (pc 6)
>   [6] w3c.jigsaw.http.Client.startConnection (pc 66)
>   [7] w3c.jigsaw.http.socket.SocketClient.run (pc 86)
>   [8] w3c.util.CachedThread.run (pc 10)
>
> and I don't know if this also matters but there are 5 active-stream
> threads which are all in the following state:
>
>   [1] java.lang.Object.wait (Object:315)
>   [2] w3c.util.CachedThread.waitForRunner (pc 37)
>   [3] w3c.util.CachedThread.run (pc 1)
>
> I would really appreciate any and all help. Thanks.
>
> -Mark
Received on Tuesday, 9 December 1997 17:04:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:27 GMT