]
Subject: Re: tomcat - request thread pool question
Hi - I was referring to the HTTP 1.1 Connector. Thanks
for the information but I am a bit puzzled as to why
the threads should go away (ie die) on getting an
exception. On a heavily loaded server, we can have
different IO exceptions being generated
Hi - I was referring to the HTTP 1.1 Connector. Thanks
for the information but I am a bit puzzled as to why
the threads should go away (ie die) on getting an
exception. On a heavily loaded server, we can have
different IO exceptions being generated all the time
and the pool will be too busy
to
applications.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Rau NF [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 3:58 PM
To: [EMAIL PROTECTED]
Subject: Re: tomcat - request thread pool question
Hi - I was referring to the HTTP 1.1 Connector. Thanks
for the information
Hi - Under what conditions can the tomcat thread pool
implementation decide to let a thread exit ?
Would this happen if some application code threw an
exception and is caught only by the tomcat framework ?
Can it happen if the servlet is writing data out to a
connection and gets a
It really depends on if you are talking about the HTTP Connector, or the AJP
Connector.
For the HTTP Connector, threads usually have short lives (i.e. they exit
after the last Keep-Alive has been handled). Exceptions thrown out of the
servlet, and certain HTTP status codes will also end the
