Pid wrote:
I am not a number!
That betrays your age too, you know that ?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
> From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com]
> Subject: RE: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
>
> [Pantvaidya, Vishwajit] Why are connections idle for a
> long time not good?
He didn't say they weren't good, he said they we
On 21.05.2009 20:59, Pantvaidya, Vishwajit wrote:
>> 3) I think I already indicated that you do not want to look at entries
>> in TIME_WAIT state. This state is special and not related to any threads
>
> [Pantvaidya, Vishwajit] My netstat o/p had FIN_WAIT and CLOSE_WAIT, but not
> TIMED_WAIT. Did
>
> 1) If you want to analyze your original problem, you need to get back to
> the original situation, i.e. without connectionTimeout. It doesn't make
> much sense to guess about the original problem by looking at something
> very different.
[Pantvaidya, Vishwajit] Yes - I have already initiated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vishwajit,
On 5/19/2009 6:08 PM, Pantvaidya, Vishwajit wrote:
>> No, Tomcat uses precisely 1 thread to handle each incoming HTTP
>> request. If keepalives are used, multiple requests may be handled
>> by the same thread before it is returned to the po
Trying to add some info below.
On 21.05.2009 05:09, Caldarale, Charles R wrote:
>> From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com]
>> Subject: RE: Running out of tomcat threads - why many threads in
>> RUNNABLEstage even with no activity
>>
>> So socket_keepalive is already 1. So does
> From: Pid [mailto:p...@pidster.com]
> Subject: Re: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
>
> I am not a number!
But are you a free man?
We want information, by hook or by crook...
(Apologies to the late Patrick McGoohan.)
- Chuck
THIS CO
Caldarale, Charles R wrote:
>> From: André Warnier [mailto:a...@ice-sa.com]
>> Subject: Re: Running out of tomcat threads - why many threads in
>> RUNNABLEstage even with no activity
>
>> if you add "-p" to netstat (at least under Linux), it will also
>> show the program that corresponds to that
> From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com]
> Subject: RE: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
>
> So socket_keepalive is already 1. So does this mean that firewall is
> dropping connections in spite of it.
The doc does not m
> This FAQ entry looks promising:
> http://tomcat.apache.org/connectors-doc/miscellaneous/faq.html
>
> Look at the entry entitled "I've got a firewall between my web server and
> Tomcat which drops ajp13 connections after some time".
>
> Configuring keep-alives is a fairly low-overhead workaround
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Subject: RE: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
> http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp?topic=/
> com.ibm.support.was40.doc/html/Plug_in/swg21163659.html
Vaguely i
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
> if you add "-p" to netstat (at least under Linux), it will also
> show the program that corresponds to that line.
Or at least -o to show the p
Pantvaidya, Vishwajit wrote:
- why do the 11 threads in the httpd o/p show port 21069 in foreign addr. Or are those not the correct threads I should be looking at?a A bit off-topic maybe, but if you add "-p" to netstat (at least under
Linux), it will also show the program that corresponds to th
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Wednesday, May 20, 2009 11:53 AM
> To: Tomcat Users List
> Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE
> stage even with no activity
>
> On 20.05.2009 1
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Wednesday, May 20, 2009 11:53 AM
> To: Tomcat Users List
> Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE
> stage even with no activity
>
> On 20.05.2009 1
On 20.05.2009 19:47, Caldarale, Charles R wrote:
>> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
>> Subject: RE: Running out of tomcat threads - why many threads
>> inRUNNABLEstage even with no activity
>>
- Setting connectionTimeout in server.xml seems to have resolved
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Subject: RE: Running out of tomcat threads - why many threads
> inRUNNABLEstage even with no activity
>
> > > - Setting connectionTimeout in server.xml seems to have resolved
> > > the issue
>
> Only because you're throwing away w
> > Yes, sure - we will upgrade at some point of
> > time. But since upgrading all our servers will be some work, that may
> > not happen right away.
>
> Upgrading mod_jk is the least painful of all of these, and the most
> likely to affect you.
>
[Pantvaidya, Vishwajit] I understand and agree an
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Monday, May 18, 2009 2:43 PM
> To: Tomcat Users List
> Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE
> stage even with no activity
>
> Yes, those two loo
Yes, those two look like "waiting for next request on an existing
connection from the web server to Tomcat" and "sitting idle in the pool,
waiting for a new connection to handle".
On 18.05.2009 22:44, Pantvaidya, Vishwajit wrote:
>>> [Pantvaidya, Vishwajit] Here are figures from 3 of the servers w
> > [Pantvaidya, Vishwajit] Here are figures from 3 of the servers which
> have
> > not yet run out of threads (so the thread count does not add up to 200).
> I
> > have taken these late at night when no users are present, so I was
> > expecting all threads to be Waiting for tomcat thread-pool
> [Pantvaidya, Vishwajit] Here are figures from 3 of the servers which have
> not yet run out of threads (so the thread count does not add up to 200). I
> have taken these late at night when no users are present, so I was
> expecting all threads to be Waiting for tomcat thread-pool.
>
> 1. Total
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vishwajit,
On 5/18/2009 2:01 PM, Pantvaidya, Vishwajit wrote:
> Yes, sure - we will upgrade at some point of
> time. But since upgrading all our servers will be some work, that may
> not happen right away.
Upgrading mod_jk is the least painful of all
On 14.05.2009 20:29, Pantvaidya, Vishwajit wrote:
> I set connectionTimeout in server.xml to 60 and now the RUNNABLE
> threads go back to WAITING stage after that time.
>
> But our other servers which are running the same configuration, same
> webapp and do not have connectionTimeout set in se
On 13.05.2009 23:28, Pantvaidya, Vishwajit wrote:
> My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using
> AJP1.3. Every 2-3 days with no major load, tomcat throws the error:
> "SEVERE: All threads (200) are currently busy, waiting..."
>
> I have been monitoring my tomcat TP-Proce
Hi Chris,
Thanks for your reply.
>
> On 5/13/2009 5:28 PM, Pantvaidya, Vishwajit wrote:
> > My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using
> > AJP1.3.
>
> Old versions of everything. Consider upgrading?
>
[Pantvaidya, Vishwajit] Yes, sure - we will upgrade at some poin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vishwajit,
On 5/13/2009 5:28 PM, Pantvaidya, Vishwajit wrote:
> My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using
> AJP1.3.
Old versions of everything. Consider upgrading?
> Every 2-3 days with no major load, tomcat throws the
: Tomcat Users List
Subject: RE: Running out of tomcat threads - why many threads in RUNNABLE stage
even with no activity
I set connectionTimeout in server.xml to 60 and now the RUNNABLE threads go
back to WAITING stage after that time.
But our other servers which are running the same
I set connectionTimeout in server.xml to 60 and now the RUNNABLE threads go
back to WAITING stage after that time.
But our other servers which are running the same configuration, same webapp and
do not have connectionTimeout set in server.xml, do not show so many RUNNABLE
threads, but more
29 matches
Mail list logo
