MustGather: Enterprise JavaBeans, Workload Management problems with WebSphere Application Server

Technote (troubleshooting)


Collecting data for problems with the IBM WebSphere Application Server enterprise bean, workload management (WLM) component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving the problem

Collecting data for problems with the IBM® WebSphere® Application Server enterprise bean, workload management (WLM) component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data using the IBM Support Assistant Data Collector

    Beginning with WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector (ISADC) tool is bundled with the product and is automatically installed. As a result, you can run the  ISADC tool directly from the app_server_root/bin directory. Note: ISADC is not bundled with the WebSphere Application Server Liberty Profile. For more details, see Using the IBM Support Assistant Data Collector.

  1. Using the ISA Data Collector:
    • To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]

      • To download, install and run ISADC locally:
      • Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server.
      • Select the option to collect from this or another system using a downloadable utility.
      • Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.

  2. Select the Runtime > Workload Management Problem collector and click Start.

  3. Follow the prompts to automatically submit the collected data to IBM Support.

Collecting data manually

Enterprise JavaBeans WLM specific MustGather information

  1. Enterprise JavaBeans WLM Server trace:
    Enable and collect Application Server traces with the trace specification.
    • For version 6.0, 6.1, 7.0, 8.0, and 8.5:


      For V6.0 with multiple core groups and one or more core group bridges


    • For version 5.x:


    If Object Request Broker (ORB) communication trace is required, see additional instructions to set ORB trace to setup.

    For detailed instructions on enabling trace, see How to setup a Trace.

  2. Enterprise JavaBeans WLM Client Trace:
    Enable client side WLM, Naming and ORB traces.

    Use the Enterprise JavaBeans WLM Server trace instructions above if the client is an application server. If the client is a J2EE or a Thin application client, then use the instructions below:
    • From a Thin application client:
      In the file install_root\properties\ file, replace the trace string with following:
      • For version 6.0, 6.1, 7.0, 8.0, and 8.5:


      • For version 5.x:

      Start your client program with the following JVM arguments to specify the trace settings: <clientProgram>

    • From a J2EE application client using launchclient utility:
      Use the following steps to collect a J2EE client trace:
      1. Backup and Edit the CLIENT_WAS_HOME/bin/ or .bat to add following as JVM arguments to Java command.

      2. Start your launchClient with trace option (-CCtrace option)
        • For version 6.0, 6.1, 7.0, 8.0, and 8.5:


        • For version 5.x:


  3. Collect the following information:
    Trace log files from the diagnostic trace from server and client side traces. Gather collector tool output by running the install_root/bin/ or the collector.bat from a location outside install_root. You can not run this utility directly from the /bin directory or any other Application Server directory. For instructions on the collector, see Running the collector tool in the V7.0 information center.

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

Additional instructions to set ORB trace
Setting the ORB Trace flag

  1. Go to the Configuration page for the server to trace.
    For Application Server, select Servers > Application Servers > server_name > Container Services
    For Node Agent, select System Administration > Node Agent > nodeagent
    For Deployment Manager, System Administration > Deployment Manager
  2. Click ORB Service under Additional Properties.
    Select the check box for ORB tracing under General Properties.

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

Related information
Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server

Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:

Read first and related MustGathers

Related information

Recording your screen to share with IBM Support

Cross reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK

Document information

More support for:

WebSphere Application Server
Workload Management (WLM)

Software version:

5.1, 6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Content navigation