IBM Support

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

Troubleshooting


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.

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.

Collecting data

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 TraceSettings.properties file found in the WebSphere Application Server install_root/properties directory into the JMX API client classpath.
       
    2. Modify the TraceSettings.properties file by changing the last line.

      From:

      com.ibm.ejs.ras.*=all=enabled

      To:

      *=all=enabled

      Also verify the location of the traceFileName file is valid.
       
    3. Add -DtraceSettingsFile=TraceSettings.properties to the JMX API client Java™ execution line. Example shown below:

      java -DtraceSettingsFile=TraceSettings.properties -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:

      com.ibm.websphere.management.*=all:com.ibm.ws.management.*=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.
     

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:

  • IBM Case
  • E-mail
  • FTP to the Enhanced Customer Data Repository (ECuRep)

Instructions for exchanging information with IBM Support

Read first and related MustGathers

MustGather: Read first for WebSphere Application Server

Administrative console problem Cluster ripple start problem Deployment problem Discovery problem on Deployment Manager Discovery problem on Node Agent Profile wizard problem Start problem Stop problem System administration problem WASService problem (Windows only) WSAdmin problem

[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000CdIhAAK","label":"WebSphere Application Server traditional-All Platforms-\u003ESystem Management-\u003ETraditional WAS-\u003EJMX \/ JAVA API Client"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.5"},{"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":"BU059","label":"IBM Software w\/o TPS"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
14 February 2024

UID

swg21196218

Page Feedback