On 05.10.2010 15:27, mamalacation wrote:
n828cl,
n828cl wrote:
Pretty much guaranteed that it's not Tomcat but your webapp that is
locking itself out of access to some resource (such as the database).
Take several thread dumps during the slowdown period and see what's going
on.
http://wiki
Op dinsdag, 5 oktober 2010 15:27 schreef mamalacation
:
n828cl,
n828cl wrote:
>
>
> Pretty much guaranteed that it's not Tomcat but your webapp that is
> locking itself out of access to some resource (such as the database).
> Take several thread dumps during the slowdown period and
n828cl,
n828cl wrote:
>
>
> Pretty much guaranteed that it's not Tomcat but your webapp that is
> locking itself out of access to some resource (such as the database).
> Take several thread dumps during the slowdown period and see what's going
> on.
>
> http://wiki.apache.org/tomcat/HowTo#Ho
> From: mamalacation [mailto:mamalacat...@hotmail.com]
> Subject: tomcat 6.0 bottleneck
> From what I understand is that my system has still adequate free physical
> resources, sql server is not being pushed and the bottleneck comes from
> tomcat, where I have no clue what to tune.
Pretty much g
...and another thing:
Yesterday, the server was running under this load, so when I checked the
manager/status today I saw that current thread count was 500 while busy
threads were only about 10. Shouldn't the threads be killed at some moment?
What is the timeout option for this behavior?
Thanx a
