I'll be presenting a WebSphere Technical Exchange on May 1st @ 11AM Eastern. The topic will be a deep dive on IBM Java Health Center, primarily around its low-overhead, production-ready profiling capabilities to understand CPU issues on IBM JVMs. The slides are already available here: http://www-01.ibm.com/support/docview.wss?uid=swg27024833&aid=1.
Kevin Grigorenko - IBM WebSphere SWAT
kgibm 0600027VAP 3,726 Views
kgibm 0600027VAP 5,019 Views
WAS exposes a JVM MBean for each process that has methods to create thread dumps, heap dumps, and system dumps. For example, to produce a thread dump on server1, use this wsadmin command (-lang jython):
The dumpThreads functionality is different depending on the operating system:
For any customers that have changed the behavior of the JVM (-Xdump) in how it responds to SIGQUIT/SIGBREAK (i.e. kill -3), then dumpThreads will respond accordingly (unless running z/OS, in which case use wsadmin_dumpthreads* properties). For anyone wishing to keep a non-default behavior for SIGQUIT/SIGBREAK but still have a scriptable way to produce only javacores, either use one of the other -Xdump events, or use a JSP that executes this method (IBM JVMs only):
There are also other ways to do this such as HealthCenter, VisualVM, etc.