> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Friday, May 22, 2009 12:39 PM
> To: Tomcat Users List
> Subject: Re: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
> > [Pantvaidya, Vishwa
ent connections are good, but connections which are
> idle for a long time are not as good, so close them after some idle
> time, like e.g. 10 minutes. Of course this means you need to create new
> ones once your load goes up again, but that's not a big problem.
[Pantvaidya, Vishwaji
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Thursday, May 21, 2009 3:37 PM
> To: Tomcat Users List
> Subject: Re: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
>
> On 22.05.2009 00:1
gt; Vishwajit,
>
> On 5/20/2009 3:01 PM, Pantvaidya, Vishwajit wrote:
> > [Pantvaidya, Vishwajit] Ok so RUNNABLE i.e. persistent threads should
> > not be an issue. The only reason why I thought that was an issue was
> > that I was observing that the none of the RUNNAB
>
> 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]
keep-alives is a fairly low-overhead workaround, but it would
> be better to fix the firewall so it doesn't silently drop connections.
>
> - Chuck
>
[Pantvaidya, Vishwajit] Thanks Chuck. My workers.properties already has
following settings:
port=21065
cachesize=10
cache_t
I am running a webapp under tomcat 5.5 with the server.xml having a Host
element as:
The webapp needs to set the system property java.endorsed.dirs to a location
like C:\myapphome\lib\endorsed.
But the setclasspath.bat that comes bundled with tomcat sets this property to
\common\endorsed. It
> > The fact that *none* of the ports match would suggest (but not prove)
> that
> > someone in the middle is closing the connections, and not telling either
> > end about it.
> >
> > Do the netstat -anop again; it should be more interesting.
> >
>
> The fact that *none* of the ports match would suggest (but not prove) that
> someone in the middle is closing the connections, and not telling either
> end about it.
>
> Do the netstat -anop again; it should be more interesting.
>
> - Chuck
>
[Pantvaidya, Vishwajit]
ed and new ones
> created.
>
> That's a good point. You should check both sides by using "netstat -an".
> The Apache side and the Tomcat side (without connectionTimeout, so you
> can see the problem in the original form). See whether the number of AJP
> connections in
d. Go do the netstat that Rainer suggested
> and let us know what you see. Stop fixating on the thread state.
>
> - Chuck
>
>
[Pantvaidya, Vishwajit] Ok will do Chuck - thanks a lot for persisting with me
through this issue.
ed and new ones
> created.
>
> That's a good point. You should check both sides by using "netstat -an".
> The Apache side and the Tomcat side (without connectionTimeout, so you
> can see the problem in the original form). See whether the number of AJP
> connections in
> >
> > [Pantvaidya, Vishwajit] My problem is that tomcat is running out of
> threads (maxthreadcount=200). My analysis of the issue is:
> > - threads count is exceeded because of a slow buildup of RUNNABLE
> threads (and not because number of simultaneous http requests
d the connection yet (something like
> HttpServletResponse.getOutputStresm.close)
>
>
> [Pantvaidya, Vishwajit] My problem is that tomcat is running out of
> threads (maxthreadcount=200). My analysis of the issue is:
> - threads count is exceeded because of a slow buildup of RUNNABLE threads
54, 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
> >>
> >> Ok - so then the question is when does
> > 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, Vis
Is there anyway to cache sets of files in multiple levels of a hierarchical
directory structure e.g.
/js/*.js
/js/1/*.js
/js/1/1/*.js
I was checking this out on the httpd side using mod_file_cache, mod_headers,
mod_expires. The Directory and other directives seem to take wildcards like *
and ?
> -Original Message-
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: Monday, May 18, 2009 4:02 PM
> To: Tomcat Users List
> Subject: RE: Running out of tomcat threads - why many threads in
> RUNNABLEstage even with no activity
>
> >
k 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".
>
[Pantvaidya, Vishwajit] Thanks Rainier. Any idea why threads would be sitting
around in Runnable st
> > [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 t
> [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.
&
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, sur
Since I did not get any responses to this, just wanted to ask - did I post this
to the wrong list and should I be posting this to the tomcat developers list
instead?
-Original Message-
From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com]
Sent: Thursday, May 14, 2009 11:29 AM
To
WAITING threads. So looks like the threads are getting
recycled properly there.
Any idea why could this be? Could it be the OS (all servers run Linux but I do
not know which flavors/versions)?
-Original Message-
From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com]
Sent
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-Processor thread behavior over extended
time intervals and observ
25 matches
Mail list logo
