> That sounds like you looked at ps or similar output, not a thread dump. Take > an actual JVM thread dump and see where the worker threads are during the > busy periods.
Wrong, to identify the thread in question I looked with Sysinternals Process Explorer which thread ID caused the 100% CPU. Then I looked up this thread ID in the Java thread dump. And this was the thread named "VM Thread". > Turn on GC logging to see if you are experiencing heap churn and heavy GC > activity. Thank you for the hint. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
