-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 MSerraInsiel,
On 3/20/2009 5:40 AM, MSerraInsiel wrote: > Hi all, We have a java web application (deployed on Tomcat 5.5 with java 1.4) > that has never had CPU problems. Take thread dumps while the CPU is pegged. You didn't mention your Java version, so here goes: - - If you have Java 1.5+, you should have the 'jstack' program. Run that targeting the pid of the top-level Java process and you should get a complete thread dump. OR - - On UNIX, send a SIGSTOP to the main java process and look at the output in catalina.out. OR - - On Windows, you'll need to press CTRL-\ when running Tomcat from the command-line. I'm not sure how else to get a thread dump from java on Windows, so if you're running it as a service, you might have to stop Tomcat, re-start it from the command line (startup.bat) and then press CTRL-\ after your CPU goes high. Take thread dumps a few seconds apart, then examine them. Threads that say "BLOCKED" are not using any CPU (at least, not at the time the thread dump was taken). Anything that says "RUNNABLE" should be inspected to see what it's doing. Post your thread dumps to the list if you can't figure out what's going on. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknDqpsACgkQ9CaO5/Lv0PAWEwCfcQ3n9YoOFKElIWqdgjf01WHZ U8EAn32cdrguG0RUOTGoUCm6vJZV9ozr =woZD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
