Return-Path: 
 <tomcat-user-return-47373-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 40605 invoked by uid 500); 12 Sep 2001 17:30:12 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
list-help: <mailto:tomcat-user-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 40589 invoked from network); 12 Sep 2001 17:30:12 -0000
Message-ID: <20010912173016.52114.qmail@web9901.mail.yahoo.com>
Date: Wed, 12 Sep 2001 19:30:16 +0200 (CEST)
From: =?iso-8859-1?q?Jean-Christophe=20Salom=E9?= <jcsalome@yahoo.fr>
Subject: bug 1006 - v3.2.3
To: tomcat-user@jakarta.apache.org
Cc: hgomez@slib.fr
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hello

We are using Tomcat 3.2.3, ibm jdk 1.2.2 (aix).
(our) Tomcat has a similar symptom than the bug 1006
described in the bug database : Tomcat standlone
accumulate blocked thread and stop responding.

Isn't it supposed to be fixed in release 3.2.2?
"------- Additional Comments From hgomez@slib.fr
2001-03-24 05:09 -------
Fixed in both 3.2.2 beta 2 and 3.3 using read timeout
of 300s (5mn)"

I have checked the code, TIMEOUT is correct (=3000)
but the patched code is incomplete :
<missing>
if (accepted != null)
{
  accepted.setSoTimeout(timeout);   
}
</missing>
if( factory != null && accepted != null)
     factory.initSocket( accepted );
}


___________________________________________________________
Do You Yahoo!? -- Un e-mail gratuit @yahoo.fr !
Yahoo! Courrier : http://fr.mail.yahoo.com