MustGather: Classloader problems for WebSphere Traditional

NOTE: Please see the following link for instructions to set classloader tracing on Websphere Liberty: 
MustGather: Classloader problems for WebSphere Application Server Liberty


Perform the following steps to collect WebSphere Application Server specific information. Please make sure you enable the JVM args. These are necessary for getting all of the information needed from the trace: 

1. 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.
       
2. 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.
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.
    
   • Gathering information with the collector tool - V8.5
   • Gathering information with the collector tool - V9.0
     
      
8. Send the collector output to IBM: Exchanging information with IBM support.
   
    

Getting started with Troubleshooting for WebSphere Application Server