IBM Support

MustGather: Java Management Extensions (JMX) API clients in WebSphere Application Server



Collecting data for problems with the Java™ Management Extensions (JMX) API clients in IBM® WebSphere® Application Server. 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 Java™ Management Extensions (JMX) API clients in IBM® WebSphere® Application Server. 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.

      • Select the Administration > JMX Problem collector and click Start.

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

Collecting data manually

Do the following to test and collect the correct information for understanding the calls made by the client program to the Application Server JMX APIs:
  1. Enable tracing on the client JMX API program.
    1. Copy the file found in the WebSphere Application Server install_root/properties directory into the JMX API client classpath.

    2. Modify the file by changing the last line.


    3. To:


      Also verify the location of the traceFileName file is valid.

    4. Add to the JMX API client Java™ execution line. Example shown below:

      java -classpath %WAS_install%\lib\admin.jar;%WAS_install%\lib\wasjmx.jar;. AdminClientExample

  2. Enable Admin tracing on the server the client program connects to as well as any other servers that will be involved, using the Administrative Console.
    1. Expand Troubleshooting and select Logs and Trace.

    2. Select the problem server and select Change Log Detail Levels.

    3. Set the trace entry to the following:**=all

    4. Make sure the Diagnostic Trace Service for this server is setup to log the information to a file.

    5. Click OK and save or synchronize changes.

  3. Stop the server(s) and clear the server(s) logs (ffdc too).

  4. Recreate the problem

  5. Run the collector tool on the problem profile(s).

  6. Collect the following files for support:
    • Collector output jar
    • JMX API client trace
    • Simple client or snippet of the problem code

  7. Follow directions in MustGather: Read First for opening a PMR and sending data to IBM Support.

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

For a listing of all technotes, downloads, and educational materials specific to the Java Management Extensions (JMX)/JMX client API 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

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java Management Extensions (JMX) or JMX client API","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.5.5;8.5;8.0;7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018