nteresting things are going to happen on larger SMP systems.
Martin
Martin Schulz wrote:
it appears that the JVM slows everything down to a crawl,
including the code path which should lead to another accept being
called., for up to 8 minutes!!!
Furthermore, the mpstat has the nice porperty that CPU usa
list only if I learn anything which impacts Tomcat
directly
(other than that the code path to hand of the socket accept responsibility
is not suitable for _very_ high hit rates, which does not worry me too
much at this point).
Cheers!
Martin
Martin Schulz wrote:
Rainer,
Thanks for the tips.
h 1.3.1_09).
In this stack dump you should be able to figure out, in which methods
most of your threads stay and what the status is.
Is there native code included (via JNI)? Any synchronization done in the
application itself? Are you using Tomcat clustering? Which JVM?
Sincerely
Rainer Jung
Martin Sc
such a scenario.
.I have kept system statistics for both scenarios and can provide these
on request.
Thanks!
Martin Schulz
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I would like to know whether I can control the cacheing
behavior of org.apache.catalina.loader.WebappClassLoader
somehow.
For the purpose of developing a server application, I would
like to be able to drop in config files and other resource
files such as scripts and be able to reload them
pro
