IBM Support

MustGather: Classloader problems for WebSphere Application Server

Troubleshooting


Problem

The following MustGather will assist you in setting up the traces and collecting the data required to analyze a classloader issue.

Resolving The Problem

Collecting data for problems with the IBM® WebSphere® Application Server classloader component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data

This MustGather is needed to analyze exceptions such as: ClassNotFoundException, NoClassDefFoundError, ClassCastException, NoSuchMethodError, LinkageError, UnsatisfiedLinkError, VerifyError, UnsupportedClassVersionError, IncompatibleClassChangeError, ClassFormatError.

Collecting data manually


NOTE: Please see the following link for instructions for Liberty Profile:
MustGather: Classloader problems for WebSphere Application Server Liberty Profile


Perform the following steps to collect WebSphere Application Server specific information.

  1. Enable and collect Application Server traces with the following trace string:

    com.ibm.ws.classloader.*=all

    For more details, see How to set up a trace.

  2. Enable Java™ Virtual Machine (JVM) classloader traces through the Admin console:

    1. Select Servers, choose Application servers and select the server you want to configure.

    2. In the Server Infrastructure section, open Java and Process Management and select Process Definition.

    3. Under Additional Properties, select Java Virtual Machine.

    4. Check the Verbose class loading checkbox.

    5. Add the following string to the Generic JVM arguments field:

      -Dws.ext.debug=true  -Dws.osgi.debug

    6. Click OK.

  3. Save the changes. Stop the server.

  4. Clear the JVM and OSGi class cache. For more details, see How to clear the WebSphere Class Caches..

  5. Backup and delete all WebSphere log files for this WebSphere process (SystemOut*.log, SystemErr*.log, native_stderr.log, native_stdout.log, startServer.log, stopServer.log and trace.log).

    The log files are located in the following directory:

    <profile_root>/logs/server_name/* 

    Clear all WebSphere Application Server FFDC logs. FFDC files are located in the following directory:

    <profile_root>/profile_name/logs/ffdc/*

    Note: If you have configured to write FFDC log files into a different location, then clear them accordingly.

  6. Restart the server. Reproduce the issue. Make sure the classloader exception is generated in the WebSphere logs (SystemOut.log) and the trace file (trace.log).

  7. Run the collector tool against the problem profile.

  8. Send the collector output to IBM: Exchanging information with IBM support.



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

Internal Use Only

The following MustGather will assist you in setting up the traces and collecting the data required to analyze a classloader issue. This MustGather is needed to analyze exceptions such as:
ClassNotFoundException, NoClassDefFoundError, ClassCastException, NoSuchMethodError, LinkageError, UnsatisfiedLinkError, VerifyError, UnsupportedClassVersionError.



    • native_stderr
    • native_stdout
    • SystemErr
    • SystemOut

    The log files are located in the following directory:
    • For V6 and V7 releases:


      install_root/profiles/profile_name/logs/server_name

    • For V5 releases:


      install_root/logs/server_name/

    Clear all WebSphere Application Server FFDC logs. FFDC files are located in the following directory:
    • For V6 and V7 releases:


      install_root/profiles/profile_name/logs/ffdc

    • For V5 releases:


      install_root/logs/server_name/ffdc

    Note: If you have configured to write FFDC log files into a different location, then clear them accordingly.

  1. Enable and collect Application Server traces with the following trace string:


    com.ibm.ws.classloader.*=all

  2. For more details, see How to set up a trace.

  3. Enable Java™ Virtual Machine (JVM) classloader and bootstrap traces through the administrative
    console for Version V5, V6 and V7.
  4. Expand Server Types, choose WebSphere Application servers and select the problem server.

  5. On right side, under Server Infrastructure, expand Java and Process Management.

  6. Click Process Definition.

  7. Under Additional Properties, select Java Virtual Machine.

  8. Check the Verbose class loading checkbox.

  9. Click Apply.

  10. On right side, under Additional Properties click Custom Properties.

  11. Click New.

  12. Enter the following custom property:
    • Name: ws.ext.debug
    • Value: true
    • Click OK.

What to do next
Once you have collected the preceding information, you can begin Analyzing the data or simply send the diagnostic information to IBM support.


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 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. 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 Runtime > Classloader Problem collector and click Start.

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

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Classloader","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;8.0;7.0","Edition":"Base;Express;Network Deployment"},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Java SDK","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","Edition":""},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":null,"Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

Document Information

Modified date:
15 June 2018

UID

swg21196187