> In TC 3.2.3 the code setSoTimeout is in
> HttpConnectionHandler !
Does that mean that TC 3.2.3 is up to date?
(which means that the bug #1006 needs to be updated in
the Bug Database).
Unfortunately, it doesn't explain why TC still
blocks...
Any clues? Anybody who faced a similar problem?
That's rather urgent, we are (were...) going to deploy
Tomcat on our production servers.
Thanks ...
--- GOMEZ Henri <[EMAIL PROTECTED]> a �crit�:
> >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 [EMAIL PROTECTED]
> >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
> >
___________________________________________________________
Do You Yahoo!? -- Un e-mail gratuit @yahoo.fr !
Yahoo! Courrier : http://fr.mail.yahoo.com
