Troubleshooting
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.
Resolving The Problem
Tab navigation
- Learning more
- Troubleshooting
- Collecting data- selected tab,
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.
Enterprise JavaBeans WLM specific MustGather information
- Run the collector tool to gather all configuration files from your Deployment Manager profile
Collector output from the Deployment Manager profile is very important for the initial investigation because most WLM problems are related to configuration issues.
You must run collector on the node that hosts the Dmgr profile so that the configuration for the entire cell is collected.
1. To run the collector script please create a temp directory on your operating system
2. Enter the /temp directory
3. Run the collector-script:
For Linux/Unix use command:
/temp>./<DMGR-profile-root>/bin/collector.sh
For example:
/temp> ./opt/IBM/WebSphere/AppServers/profiles/Dmgr/bin/collector.sh
For Windows use command:
C:\temp> C:\<DMGR-profile-root>\bin\collector.bat
For example:
C:\temp> C:\IBM\Websphere\AppServers\profiles\Dmgr\bin\collector.bat
4. The command will create a jar-file in the temp directory. Please send us the output jar file.
If you need further assistance with the collector-tool, please read:
Running the collector tool
- Enterprise JavaBeans WLM Server trace:
Enable and collect Application Server traces with the trace specification.
For version 7.0, 8.0, 8.5 and 9:
WLM*=all:ORBRas=all
If Object Request Broker (ORB) communication trace is required please check detailed instructions in document:
MustGather: Object Request Broker (ORB) problems with WebSphere Application Server
(section: Collecting data manually -> Enabling Comm Trace)
For detailed instructions on enabling trace, see How to setup a Trace.
- 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\TraceSettings.properties file, replace the trace string with following:
WLM*=all:ORBRas=all
Start your client program with the following JVM arguments to specify the trace settings:
-Dcom.ibm.CORBA.Debug=true
-DtraceSettingsFile=TraceSettings.properties <clientProgram>
- From a J2EE application client using launchclient utility:
Start your launchClient with the following trace-option:
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-CCtrace=WLM*=all:ORBRas=all
-CCtraceMode=basic
For example:
install_root/bin/launchClient.sh <ear_file> -JVMOptions="-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true" -CCtrace=WLM*=all:ORBRas=all -CCtracefile=orbtrace.txt -CCtraceMode=basic
For more details, please check document:
MustGather: WebSphere Application Server Client problems in 8.5, 8.0, 7.0, 9.0
- Collect the following information:
- collector output from the Deployment Manager profile.
filename: host_name-cell_name-node_name-profile_name.jar
- all log- and trace-files located in folder:
profile_root/logs/server_name/
- all ffdc-files located in folder:
profile_root/logs/ffdc folder
Follow instructions to send diagnostic information to IBM support.
| 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 |
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 Support Assistant (ISA)
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Workload Management (WLM)","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;8.0;7.0;6.1;6.0;5.1","Edition":"","Line of Business":{"code":"LOB45","label":"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"}}]