MustGather: Overview of Application Server, Node Agent, Deployment Manager hang problems
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server Hangs/Performance Degradation component. 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.


Hangs/Performance Degradation specific MustGather information for the following:
  • 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 above processes represent a Java Virtual Machine (JVM™). For all the Java Virtual Machine (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. "Appendix A: How to collect JVM thread dump for the server in hang"
  2. Collector tool output
    • Running the collector tool V6.0
    • Running the collector tool V5.1
    • Running the collector tool V5.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:
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Hangs/Performance Degradation
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1141514
IBM Group: Software Group
Modified date: May 21, 2008