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

Re: Client disconnect after 2 days

From: Yves Lafon <ylafon@w3.org>
Date: Fri, 12 Mar 1999 15:12:50 +0100 (MET)
To: M Ranga Rao Choudary <mrrc@wipinfo.soft.net>
cc: www-jigsaw@w3.org
Message-ID: <Pine.GSO.4.10.9903121454040.27037-100000@tarantula.inria.fr>
On Fri, 12 Mar 1999, M Ranga Rao Choudary wrote:

> hi all,
> 
> We are writing a heavy load web based application using Jigsaw as the
> http server. We are running the Jigsaw using the JRE1.1.6.
> 
> The initial JAR file size is 2.1 MB. We are using Voyager ORB for
> remote enabling the objects.. The client is supposed to connect to the
> server for 365 days year, very critical application. But the client is
> disconnecting after 2 days. We were not able to connect more than 5
> clients.  Our requirement is connecting atleast 35 clients.

There shouldn't be any problem with the number of clients, you just have
to select the right number of clients available in the
SocketConnectionProperty property sheet.
The default should be 30 clients max, and must be bumped.

For the timeout, it is set by a property, to avoid "eaten" threads caused
by undetected socket close.
The property controlling it is org.w3c.jigsaw.request.timeout
(It is in the http-server.props)
in milliseconds. If you set it to 1000*86400*365, you're all set.
Regards,

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Friday, 12 March 1999 09:13:25 GMT

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