W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1999

Re: max_conn and timeout

From: Yves Lafon <ylafon@w3.org>
Date: Fri, 30 Apr 1999 17:20:49 +0200 (MET DST)
To: Giannakopoulos Michalis <mgi@elca.ch>
cc: www-jigsaw@w3.org
Message-ID: <Pine.GSO.4.10.9904301718001.13031-100000@tarantula.inria.fr>
On Fri, 30 Apr 1999, Giannakopoulos Michalis wrote:

> Hi!
> 
> just to say that properties (for example set to)
> 
> org.w3c.www.protocol.http.connections.max=2
> org.w3c.www.protocol.http.connections.timeout=10000
> 
> in the http-server.props file are not fully taken into account.
> 
> I've added some debug messages in HttpBasicConnection.java, and it shows
> that when the socket.setSoTimeout(timeout) method is called, timeout is set
> to the default value (300000) and not to 10000.
> 
> About conn_max, in HttpManager, with debug flag set to true, it shows
> something like 
> 
> +++ notify conn_count 3 / 2
> 
> where 3 is conn_count and 2 conn_max...
> and 3 connections are effectively created instead of the 2 I want.

Yes, it will generate 3 connections but just after the creation of the
third, one should be killed. 
I will look into that (you can try to patch HttpManager and change 
    protected synchronized boolean tooManyConnections() {
	return conn_count > conn_max;
    }
to 
    protected synchronized boolean tooManyConnections() {
	return conn_count >= conn_max;
    }
But I need to take a closer look before sending the right patch ;)

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Friday, 30 April 1999 11:24:18 GMT

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