W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 2001

RE: HttpManager hangs.

From: Colin Gerety <colin@fastwater.com>
Date: Tue, 21 Aug 2001 20:40:44 -0400 (EDT)
Message-ID: <02f201c12aa3$097f2d50$0400000a@COLINFASTWATER>
To: <www-jigsaw@w3.org>
> > Hi - heres a stack trace of the process when it has locked up.
> > I just hit exit on the command prompt - forcing this text up.
> 
> Can you retry with a modification of the
> org.w3c.www.protocol.http.connections.max property?
> By default it should be around 5, please try with something better like
> 100
> (edit http-server.props, or it should be available from the Proxy perperty
> (>max connections).


   We are having a similar problem with client code  hanging in HttpManager.waitForConnection.  In our case, upping the connections.max property delays the hang, but does not get rid of it.  We have multiple threads using the same HttpManager.  One of our engineers put logs into several classes of Jigsaw pkg to see whether connections get closed.  he reports they seem to close and the connection objects are collected by GC.  The sockets also seem to be cleaned.
 
Colin Gerety
colin@fastwater.com
Received on Wednesday, 22 August 2001 05:54:27 GMT

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