IBM Support

MustGather: Logging Problems in IBM WebSphere Application Server

Troubleshooting


Problem

This document describes how to collect diagnostic data when IBM WebSphere Application Server logging fails to record the correct information in WebSphere or JVM specific log files. This document should also be used when collecting data for Jakarta Commons Logging (JCL) related issues.

Symptom

Incorrect output in WebSphere or JDK related logs.

Resolving The Problem

Tab navigation

This document describes how to collect diagnostic data when IBM WebSphere Application Server logging fails to record the correct information in WebSphere or JVM specific log files. This document should also be used when collecting data for Jakarta Commons Logging (JCL) related issues.

For all logging related issues please submit the folllowing data to IBM Support:

  • sample application
  • output from collector tool
  • trace with com.ibm.ejs.ras.*=all:com.ibm.ws.classloader.*=all
    For details, see How to set up a trace
  • 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
    6. Click OK.


Custom Logging

The best means of determining the cause to a logging problem where customized logging is used will be by having a sample application. This is especially true for log4j where many different configurations can be used. In addition to a sample application, the following files are also useful.

JSR47 Logging
  • Source for the customized formatters or handlers and a small coding example of how the logger is invoked.
  • logging.properties (if used)

Jakarta Commons Logging (JCL) wrapping log4j
  • The org.apache.commons.logging.LogFactory file in META-INF/services
  • commons-logging.properties file that is in the application classpath
  • version number of JCL being used (check Manifest.MF file in commons-logging.jar and look for "Implementation-Version: X.X.X" where X.X.X is the version)

WebSphere Application Server logging (SystemOut.log/trace.log/etc.):
  • To troubleshoot problems related to log rotation and log cleanup, you can enable the com.ibm.ejs.ras.* trace on the RAS component.
    Note: When a trace log rotates, a rasDebugLogger<timestampinms>.log file is generated in the temporary folder of the operating system. For example, /tmp folder for Unix and C:\temp folder for Windows operating system. This file continues to exist even if the JVM process under which it was created stops. When the JVM process restarts, a new rasDebugLogger file is generated. This file is used to debug logging and should not be deleted.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","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":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21321060