IBM Support

MustGather: Overview of Application Server, Node Agent, Deployment Manager hang problems

Troubleshooting


Problem

Collecting data for problems with the IBM WebSphere Application Server hangs or performance degradation. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving The Problem

If you already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


Collecting data for hangs or performance degradation:

  • Application Server - Extend a Web server's capabilities to handle Web application requests, typically using Java™ technology. An application server makes it possible for a server to generate a dynamic, customized response to a client request. The Application Server product provides multiple application servers that can be either separately configured processes or nearly identical clones.

  • Node Agent - Node agents are administrative agents that represent a node to your system and manage the servers on that node. Node agents monitor application servers on a host system and route administrative requests to servers. A node agent is created automatically when a node is added to a cell.

  • Deployment Manager - Deployment managers are administrative agents that provide a centralized management view for all nodes in a cell, as well as management of clusters and workload balancing of application servers across one or several nodes in some editions. A deployment manager hosts the administrative console. A deployment manager provides a single, central point of administrative control for all elements of the entire Application Server distributed cell.

All of the preceding processes represent a Java Virtual Machine (JVM™). For all the JVM hang issues, collect the following information. There is a list of links provided at the bottom of this document that routes you to the how-to documents for steps that require additional instructions.
  1. Thread Dump from the hung JVM. See Appendix A: How to collect JVM thread dump for the server in hang at the end of this page.

  2. Collector tool output.
    • Running the collector tool - V9.0
    • Running the collector tool - V8.0
    • Running the collector tool - V7.0

  3. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the component, search the WebSphere Application Server support site.

Appendix A: How to collect JVM thread dump for the server in hang


Identify the PID and follow the instructions in the appropriate technotes to collect the required thread dump.

Additional information

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Hangs\/Performance Degradation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21141514