IBM Support

MustGather: Problems during deployment of EAR/JAR/WAR files in WebSphere Application Server Traditional



Collecting data for problems with the IBM WebSphere Application Server for problems that occur during the installation of an application (EAR/JAR/WAR) environment. Gathering this MustGather information before calling IBM® Support helps you to understand the problem and save time analyzing the data.



Resolving The Problem

Tab navigation

Types of Issues:

Tab navigation

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:
a. In the administrative console, navigate to "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 Node Agent process.

c. In the Change Log Detail Levels, modify the existing trace string to:

d. If the issue is coming from annotation scanning, modify the existing trace string to:

e. Click Apply or OK so that the trace string is saved.
a. Modify the file located in the following directory:
profile_root / properties
b. Replace the following line:*=all=enabled

To following line:****=all=enabled
If the issue is coming from annotation scanning, replace with following line instead:******=all=enabled

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:
Collect the following to send to IBM® Support:
  • 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.
Follow instructions to send diagnostic information to IBM® Support.

For a listing of all technotes, downloads, and educational materials specific to the Deployment component, search the WebSphere Application Server support site.


[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Deploy (for example: AAT or ANT or EAR\/WAR\/JAR)","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;Network Deployment","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"}}]

Document Information

Modified date:
15 January 2021