Troubleshooting
Problem
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:
- Enable tracing on the client JMX API program.
- Copy the TraceSettings.properties file found in the WebSphere Application Server install_root/properties directory into the JMX API client classpath.
- 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.
- 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
- Copy the TraceSettings.properties file found in the WebSphere Application Server install_root/properties directory into the JMX API client classpath.
- 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.
- Expand Troubleshooting and select Logs and Trace.
- Select the problem server and select Change Log Detail Levels.
- Set the trace entry to the following:
com.ibm.websphere.management.*=all:com.ibm.ws.management.*=all
- Make sure the Diagnostic Trace Service for this server is setup to log the information to a file.
- Click OK and save or synchronize changes.
- Expand Troubleshooting and select Logs and Trace.
- Stop the server(s) and clear the server(s) logs (ffdc too).
- Recreate the problem
- Run the collector tool on the problem profile(s).
- Collect the following files for support:
- Collector output jar
- JMX API client trace
- Simple client or snippet of the problem code
- Follow directions in MustGather: Read First for opening a PMR and sending data to IBM Support.
- Follow instructions to send diagnostic information to 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
- FTP to the Enhanced Customer Data Repository (ECuRep)
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
Related Information
Was this topic helpful?
Document Information
Modified date:
14 February 2024
UID
swg21196218