On 22.12.2009 12:58, Pid wrote:
On 22/12/2009 11:34, DOrlov wrote:
Pid Ster wrote:
Any chance you can upgrade to the most recent Tomcat?
How much total physical RAM do you have?
Examine the heap "jmap -heap<pid>", and post the results.
I have 8Gb RAM on the machine.
PS Old Generation
47.376815763383185% used
PS Perm Generation
60.829337266299945% used
Looks OK.
To make sure the OP doesn't get confused: it looks OK at the moment the
data was collected. It could still well be, that during the time the
performance problem occurs, it is GC related. So proceed with activating
the GC log, because it is the best way to analyze what happened with GC
after something unexpected occured.
All other questions of PID are of course also valid.
Another thing you can do: if the problem lasts long enough and you have
a chance to catch such long running requests in flight, take thread
dumps, e.g.
kill -QUIT pid
where pid is the process id of your Tomcat Java process. Take two or
three of them. The results will go to catalina.out.
If something in your code is waiting, you will find that in the dump.
Those thread dumps are very different from heap dumps. Thrad dumps are
quick, produce text output and do not disturb the application
noticeably. Heap dumps are something much heavier which stop the
application for quite some time.
So if you want to get acquainted with thread dumps, you can do them even
before the problem, look at them and learn what they contain.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
