Dumping threads in server processes using scripting
Use the AdminControl object to produce a Java core dump, which includes the Java threads of a running server.
Before you begin
Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client using wsadmin scripting article for more information.
About this task
The dumpThreads command generates a Java heap dump, a Java virtual machine (JVM) initiated System Transaction Dump (TDUMP), and a Java core dump.
- A Java heap dump includes all of the live objects on the Java heap that are being used by the running Java application.
- A system TDUMP includes the content of all of the failing address spaces. Avoid trouble: In some circumstances, the hung thread detection process might be frequently triggered, causing system TDUMPs to be initiated. These dumps can be large and take several minutes to process. While the dumps are being processed, the server address space is not dispatchable, which might extend the length of time locks owned by the address space are held. If your server uses shared sub-systems like DB2 or WebSphere MQ, the extended length of time during which the locks might be held could adversely effect those shared sub-systems, and other address spaces that share those sub-systems. Therefore, if you experience frequent hung threads, you might want to disable the taking of system TDUMPs on the application server experiencing the hung threads.
- A Java core dump includes all of the memory that is being used by the JVM, and includes the state of every thread in the server processes.
If you want to disable the generation of the heap dump, set the wsadmin_dumpthreads_enable_heapdump environment variable to 0. If you want to disable the generation of the system TDUMP, set the wsadmin_dumpthreads_enable_javatdump environment variable to 0. You can set these variables at either the node or cell level.
set jvm [$AdminControl completeObjectName type=JVM,process=server1,*] $AdminControl invoke $jvm dumpThreads
jvm = AdminControl.completeObjectName('type=JVM,process=server1,*') AdminControl.invoke(jvm, 'dumpThreads')
You can also use the Modify command to generate a Java core dump whenever a timeout occurs.