IBM Support

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

Troubleshooting


Problem

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 will help you understand the problem and save time analyzing the data.

Resolving The Problem

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 will help you understand the problem and save time analyzing the data.

To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data using the IBM Support Assistant Data Collector

    Beginning with WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector (ISADC) tool is bundled with the product and is automatically installed. As a result, you can run the ISADC tool directly from the app_server_root/bin directory. Note: ISADC is not bundled with the WebSphere Application Server Liberty Profile. For more details, see Using the IBM Support Assistant Data Collector.


  1. Using the ISA Data Collector:
    • To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]

      • To download, install and run ISADC locally:
      • Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server.
      • Select the option to collect from this or another system using a downloadable utility.
      • Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.

      • Select the Administration > Deployment Problem collector and click Start.

      • Follow the prompts to automatically submit the collected data to IBM Support.

Collecting data manually

  1. Collect a copy of the application (EAR/WAR/JAR) which is having the problem so support might be able to recreate.

  2. If possible, stop all WebSphere 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:
  • For Application Server versions v7.0, v8.0, v8.5, and v9.0 :

  • 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 as well.


    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:
    e.
    *=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
    a.
    b.
    c. Click Apply or OK so that the trace string is saved.


    4. If you are using wsadmin, enable the following tracing:
    e. Modify the wsadmin.properties file located in the following directory:

    profile_root/properties


    f. Replace the following line:
    #com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled

    g. To following line:
    h.
    com.ibm.ws.scripting.traceString=com.ibm.ws.scripting.AdminAppClient.*=all=enabled:com.ibm.ws.scripting.AbstractShell.*=all=enabled:com.ibm.ws.management.*=all=enabled:com.ibm.websphere.management.*=all=enabled
    a.
    b. If the issue is coming from annotation scanning, replace with following line:
    com.ibm.ws.scripting.traceString=com.ibm.ws.scripting.AdminAppClient.*=all=enabled:com.ibm.ws.scripting.AbstractShell.*=all=enabled:com.ibm.ws.management.*=all=enabled:com.ibm.websphere.management.*=all=enabled:com.ibm.config.eclipse.wtp=fine=enabled:com.ibm.ws.metadata.annotations.*=all=enabled:com.ibm.ws.websvcs.annotations.*=all=enabled

    1. Recreate the problem.


    2. Save a screen capture of the administrative console if an error is displayed on the console screen.


    3. Run the collector tool.

    Note: If you are running in a Network Deployment environment, run on both Network Deployment and base. For more details, see the following Information Center topic:
  • Gathering information with the collector tool - V8.5
  • Gathering information with the collector tool - V8.0
  • Gathering information with the collector tool - V7.0

  • 1. 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 install 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.


  • 1. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Deploy 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


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:


Read first and related MustGathers

[{"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.0;7.0;6.1","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 June 2018

UID

swg22010614