MustGather: Read first for WebSphere Application Server

Collect troubleshooting data for problems with IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Automated collection of troubleshooting data

Automated data collectors are now available in the IBM Support Assistant to improve accuracy of complete data collection.

IBM Support Assistant Lite	IBM Support Assistant Workbench
Download | Demo | Learn more	Download | Demo | Learn more
A special offering that contains just the data collector component of the IBM Support Assistant Workbench	For a full range of problem solving features, the workbench contains all the data collection capability of ISA Lite plus much more!

Collection of troubleshooting data

Gathering general information For IBM WebSphere Application Server V5.0.2 or later, use the collector tool to capture general information for each host machine. If you are running a version prior to V5.0.2, you can also manually collect the general information. For releases of WebSphere Application Server previous to V5.0.2, manually gather the following information for each host machine: Hostname The product and version of the Web server, if one is installed The application server or clone, if either are installed The WebSphere Application Server version and edition The installed Interim Fixes Your operating system and version The operating system patches or maintenance level The number of CPUs that you have The amount of RAM that you have Entering "Collector -summary" output into an electronically-opened PMR (SR) eliminates waiting on the phone to provide general information to Level 1 support. Gathering component specific information For assistance in help identifying the component causing problems, visit the Troubleshooting Guide for WebSphere Application Server. Otherwise, take a look at the components and the component descriptions in the table below. If one of the product components below matches your symptom or the part of the product with which you are experiencing problems, follow the instructions in the associated MustGather document: 100% CPU Usage Administrative Console (all non-scripting) Administrative Scripting Tools (for example: wsadmin or ANT) Application Client Application Server Toolkit Classloader Crash Data Replication Services DB Connections/Connection Pooling Deploy (for example: AAT or ANT or EAR/WAR/JAR) Double Byte Character Set (DBCS) Dynamic Cache Edge Component EJB Container General Hangs/Performance Degradation High Availability (HA) HTTP Transport IBM HTTP Server Install Java Management Extensions (JMX) or JMX client API Java Message Service (JMS) Java Security (JSSE/JCE) Java Transaction Service (JTS) Java SDK JNDI/Naming JSP Migration Object Level Trace/Distributed Debugger (OLT/DD) Object Request Broker (ORB) Out of Memory PD tools (for example Log Analyzer) Plug-in Plug-in (remote) Install PMI/Performance Tools Programming Model Extensions (PME) Proxy server Scheduler Security Service Integration Technology Servlet Engine/Web Container Sessions and Session Management System Management/Repository Web Services (for example: SOAP or UDDI or WSGW or WSIF) Web Services Security Workload Management (WLM) Submitting information to IBM Support After a PMR is open, you can submit diagnostic MustGather data to IBM. If using SR, update the PMR to indicate that data has been sent. Related information Exchanging information with IBM Technical Support Steps to getting support for WebSphere Application Server Troubleshooting guide for WebSphere Application Server MustGather: Read first for WebSphere Application Server for z/OS MustGather: Read first for WebSphere Extended Deployment MustGather: Read first for IBM HTTP Server MustGather: Read first for WebSphere Process Server MustGather: Read first for WebSphere MQ V5.3, V5.3.1 and V6.0 MustGather: Read first for IBM WebSphere Portal