Troubleshooting
Problem
Symptom
Resolving The Problem
Tab navigation
- Learn more
- Troubleshoot
- Collect data- selected tab,
Types of Issues:
Tab navigation
- WebSphere Application Server Traditional- selected tab,
- Liberty
1. Collect a copy of the application (EAR/WAR/JAR) which is having the problem so support might be able to re-create.
2. If possible, stop all WebSphere Application Server processes and clear the following directory:
profile_root / logs
3. Restart the Deployment Manager or Application Server process.
4. Set the following Runtime mode trace:
"Troubleshooting > Logs and Trace > dmgr > Diagnostic Trace > Change Log Detail Levels".
b. Select the Runtime tab.
Note: If you are in a Base environment, select server1 instead of the dmgr server. If the problem is the application is not expanded to the installedApps directory, then also enable the traces on the nodeagent process.
c. In the Change Log Detail Levels, modify the existing trace string to:
*=info:com.ibm.ws.console.app*=all:com.ibm.ws.management.application.*=all:com.ibm.websphere.management.application.*=all
|
d. If the issue is coming from annotation scanning, modify the existing trace string to:
*=info:com.ibm.ws.console.app*=all:com.ibm.config.eclipse.wtp=finer:com.ibm.ws.ecs=finer:com.ibm.config.annotations=finer:com.ibm.ws.management.application.*=all:com.ibm.websphere.management.application.*=all
|
e. Click Apply or OK so that the trace string is saved.
profile_root / properties
#com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
|
with the following line:
com.ibm.ws.scripting.traceString=com.ibm.ws.scripting.AdminAppClient*=all:com.ibm.ws.scripting.AbstractShell*=all:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all
|
com.ibm.ws.scripting.traceString=com.ibm.ws.scripting.AdminAppClient*=all:com.ibm.ws.scripting.AbstractShell*=all:com.ibm.ws.management.*=all:com.ibm.websphere.management.*=all:com.ibm.config.eclipse.wtp=fine:com.ibm.ws.metadata.annotations.*=all:com.ibm.ws.websvcs.annotations.*=all
|
6. Recreate the problem.
7. If an error is displayed on the console screen, save a screen capture of the error in the administrative console.
8. Run the collector tool.
Note: If you are running in a Network Deployment environment, run on both Network Deployment and Node profiles. For more information, see the following Information Center topic:
- Gathering information with the collector tool - V9.0
- Gathering information with the collector tool - V8.5
- Collector outputs from step 8.
- Specific EAR/WAR/JAR file that is causing the problem
- A clear description of what options are chosen during the installation process
(If you are using a script to install the application, include it as well). - A screen capture of the administrative console if the error is displayed on the console screen.
For a listing of all technotes, downloads, and educational materials specific to the Deployment component, search the WebSphere Application Server support site.
Related Information
Exchanging information with IBM Technical Support for problem determination
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting Tips for WebSphere Application Server v9.0
Was this topic helpful?
Document Information
Modified date:
05 March 2024
UID
swg21199344