If using WebSphere Application Server, you can generate a system dump for a node to get an image of the memory of the application during runtime.
You can also generate a system dump for a cluster. Generating a cluster-level system dump creates a separate system dump file for each node in the cluster. The name and location of each system dump file display in the log of the corresponding node.
System dumps execute asynchronously, both for clusters and individual nodes.
If your environment file includes the
statAvailability attribute, ensure that it is set to distributed to enable thread dumps at the cluster level.
To generate a thread dump for a node:
- In NexJ System Admin Console, navigate to the Statistics page.
- In the list in the Statistics area, locate and expand the node on which to generate the system dump, and select Diagnostics. For example, navigate to:
application_name>/<node_name>/DiagnosticsAvailable commands display in the details area on the bottom right.
- Double-click the dumpSystem command in the details area. The Invoke dumpSystem command dialog opens.
- Click Invoke. The system dump executes. If the system dump is for the current node, the location of the dump file displays in the Result area, and the name and location of the dump file display in the log. If the system dump is for a different node, the name and location of the dump file display in the log of the node.
- Click the Close button on the top right corner of the dialog. The Invoke dumpSystem command dialog closes.
You have generated a system dump for a node.