IBM Support

PI22281: APPLICATION STARTUP FAILED WHILE INITIALIZING MYFACES WITH COMMONS-LOGGING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The application startup fails with the below error when using
    WebSphere Application Server MyFaces implementation with the
    application logging:
    
    [6/19/14 17:01:44:961 CDT] 00000040 AbstractFaces E   An error
    occured while initializing MyFaces:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException: Class
    org.apache.commons.logging.impl.Log4JLogger does not implement
    Log
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException: Class
    org.apache.commons.logging.impl.Log4JLogger does not implement
    Log
    at org.apache.commons.logging.impl.LogFactoryImpl
    .newInstance(LogFa ctoryImpl.java:532)
    at org.apache.commons.logging.impl.LogFactoryImpl
    .getInstance(LogFa ctoryImpl.java:272)
    at org.apache.commons.logging.LogFactory
    .getLog(LogFactory.java:414 )
    at org.apache.commons.digester
    .Digester.<init>(Digester.java:308)
    at org.apache.myfaces.config.impl.digester
    .DigesterFacesConfigUnmarshallerImpl
    .<init>(DigesterFacesConfigUnmarshallerImpl.java:42)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server version    *
    *                  8.0 and 8.5.5 users of JavaServer Faces     *
    *                  (JSF) MyFaces 2.0.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application-bundled JCL                 *
    *                      commons-logging implementations such    *
    *                      as Log4J can conflict with the          *
    *                      WebSphere-provided commons-logging      *
    *                      implementation when the application     *
    *                      classloader mode is set to              *
    *                      parent_last.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There can be a classloading conflict when an application
    bundles a JCL (commons-logging) implementation, with the
    application classloader mode set to PARENT_LAST.  This is due
    to a conflict with the WebSphere-provided commons-logging
    implementation.  An error such as
    AbstractFaces E   An error occured while initializing MyFaces:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException: Class
    org.apache.commons.logging.impl.Log4JLogger does not implement
    Log
    ...
    can be thrown, and MyFaces may fail to initialize.
    

Problem conclusion

  • The JSF MyFaces code was updated to allow for the correct
    loading of application-provided commons-logging
    implementations.  To enable this updated behavior, set the
    following JVM custom property to "true":
    com.ibm.ws.jsf.get.facesConfig.via.WAS.classloader
    (true/false-default)
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.10 and 8.5.5.4.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI22281

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-17

  • Closed date

    2014-08-11

  • Last modified date

    2015-08-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022