you wanna support 700 concurrent connections on 150 threads?
maxThreads==max number of concurrent connections
but in your case, put in a profiler, and that will tell you very quickly
what is causing the CPU spikes.
Filip
opensta wrote:
One more Question ::
for Tomcat config file these are
One more Question ::
for Tomcat config file these are default settings ::
maxThreads="150"
minSpareThreads="25"
maxSpareThreads="75"
enableLookups="false"
redirectPort="8443"
acc
All tomcat internal threads seem to be safe, I can see no unusual state
for them.
There are three threads in stacks coming from the package
com.hedgeflex.core.common.event.* and another three coming from Fiorano.
You should have a look at these, but they are not really good ones for a
tomcat
Use Ctrl Break at your cmd shell.
regards
Peter
Am 13.04.2006 um 11:05 schrieb Ronald Klop:
Do 'kill -QUIT ' and look in your logs for the
stacktraces about what thread is doing what.
Or run 'jstack '.
This works on Unix/Linux. I don't know how to do this on Windows.
Ronald.
On Thu A
Do this a couple of times and see which thread stays the same and which one
changes it stack. That's probably the one which is doing things.
Ronald.
On Thu Apr 13 11:01:01 CEST 2006 Tomcat Users List
wrote:
I already done that dump using that kill quit command
but how can i identify the
Do 'kill -QUIT ' and look in your logs for the stacktraces
about what thread is doing what.
Or run 'jstack '.
This works on Unix/Linux. I don't know how to do this on Windows.
Ronald.
On Thu Apr 13 09:27:36 CEST 2006 Tomcat Users List
wrote:
In our application , jboss app server , fio
I already done that dump using that kill quit command
but how can i identify the problem , following is the thread dump , please
help me how to look into
Full thread dump Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode,
sharing):
"Thread-1500" prio=1 tid=0xac187838 nid=0x2b85 waiting on co
Use the tool of your choice (depending on your platform) to find out,
which threads are using the cpu time. The do a Java Thread Dump and have
a look at it.
For *nix use ps (or prstat on Solaris) to find out about the threads.
Use kill -QUIT to write a thread dump to STDOUT (which you should
