From tomcat-user-return-47462-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Thu Sep 13 15:48:36 2001 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 46014 invoked by uid 500); 13 Sep 2001 15:48:35 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Delivered-To: moderator for tomcat-user@jakarta.apache.org Received: (qmail 4577 invoked from network); 13 Sep 2001 14:16:20 -0000 Message-ID: From: GOMEZ Henri To: =?iso-8859-1?Q?Jean-Christophe_Salom=E9?= , tomcat-user@jakarta.apache.org Subject: RE: bug 1006 - v3.2.3 Date: Thu, 13 Sep 2001 16:16:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >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. In TC 3.2.3 the code setSoTimeout is in HttpConnectionHandler ! >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 : > >if (accepted != null) >{ > accepted.setSoTimeout(timeout); >} > >if( factory != null && accepted != null) > factory.initSocket( accepted ); >} > > >___________________________________________________________ >Do You Yahoo!? -- Un e-mail gratuit @yahoo.fr ! >Yahoo! Courrier : http://fr.mail.yahoo.com >