- From: Mark Friedman <mark@intraspect.com>
- Date: Thu, 20 Nov 1997 10:56:24 -0800
- To: Jigsaw Mailinglist <www-jigsaw@w3.org>, jigsaw@w3.org
Received on Thursday, 20 November 1997 14:03:09 UTC
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 Thursday, 20 November 1997 14:03:09 UTC