cas.log not being updated when running Sites in WebSphere (Doc ID 1484401.1)

Last updated on MARCH 29, 2023

Applies to:

Symptoms

- There is no logging output in the cas.log.
- logging for the cas application is output to the System.out log for WebSphere.

- The SystemErr.log may also contain some errors related to the cas logging.  See the following for a sample stacktrace that might be seen:

e.x.

log4j:ERROR Could not parse url [wsjar:file:/<deployed app path>/ContentServer.ear/cs.war/WEB-INF/lib/docx4j.jar!/log4j.xml].
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
    at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
    at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
    at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
    at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:861)
    at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773)
    at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:483)
    at org.apache.log4j.LogManager.<clinit>(LogManager.java:127)
    at java.lang.J9VMInternals.initializeImpl(Native Method)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:233)
    at org.apache.log4j.Logger.getLogger(Logger.java:104)
      .
      .
      .

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.