Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <003f01c33ee7$772fe1a0$d2b32b04@dslverizon.net>
From: "Bill Barker" <wbarker@wilshire.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
References: <3EFFF2EF.F6824C0E@tid.es>
Subject: Re: decrease idle threads in the pool faster... (II)
Date: Mon, 30 Jun 2003 02:10:33 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit


----- Original Message -----
From: "Carlos Rodr�guez Colino" <carlosr@tid.es>
To: <tomcat-dev@jakarta.apache.org>
Sent: Monday, June 30, 2003 1:21 AM
Subject: decrease idle threads in the pool faster... (II)


>
> Hi everybody
>
> I have been searching previous mails about killing idle threads, and I
> found lots of them describing the same problem (lots of requests carry
> out new threads that never are released, so, in a long-term, max number
> of proccesses is reached and Tomcat stops). Some surprising answers were
> such as:
>
> "Yes, no attempt is being made at killing processing threads that
> were created. OTOH, they should be reused if some high load situation
> occurs
> again (no new threads will be created).
> Unless you're really short on OS resources, I don't see that being a
> huge
> problem.
>
> Remy"  (12/2001... about TC4.0.1)
>
>
> Do you keep thinking the same? It seems to be a serious problem from my
> point of view!! Burst of requests increase the number of threads used by
> Tomcat (I work nowadays with TC4.1.12), but I think they should be
> released later on. Must they grow until infinite????? Must I set
> maxProcessors to 100000000 for avoiding "Max number of processes
> reached"??? :-P A very complex system relies on Tomcat and a lot of
> servlets, so I need a solution.
>
> Some mails, like mine, proposed to dive in the code to change the
> management of idle threads and kill them. If there isn't any scheduled
> action about this problem, could anybody give me a hint about where to
> look in the code?


Well, the place to look is
j-t-c/util/java/org/apache/tomcat/net/PoolTcpEndpoint.java.  With my
experience, it works very well with the stand-alone connector.  On one very
old (and brain-dead) Linux system, I had to set a soTimeOut for the
Jk-Connector to get it to kill-off Threads (but this is really a work-around
to a problem with that Linux version).

>
> Thanks in advance and best regards,
>
> Carlos.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org