IBM Support

PI47898: Bean property initialization fails with a org.apache.commons.logging.LogConfigurationException.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Bundling a commons-logging implementation with an application
    can conflict with the WebSphere-provided commons-logging
    implementation, and can cause problems when we are trying to
    initialize the properties of a managed bean.
    /opt/WebSphere8/AppServer/plugins
    /com.ibm.ws.prereq.commons-logging .jar
    WebSphere version: ND 8.5.5.5
    Operating system version: Linux, version
    2.6.32-504.8.1.el6.x86_64
    Java version: 1.6.0, Java Runtime Version =
    pxa6460_26sr8fp3-20141218_02 (SR8 FP3)
    Stack Product/Version BPMPC 8.5.6.0 20150304-164853
    [19/08/15 10:59:44:913 BST] 000001a0 ServletWrappe E
    com.ibm.ws.webcontainer.servlet.ServletWrapper service
    SRVE0014E:
    Uncaught service() exception root cause Faces Servlet:
    javax.servlet.ServletException:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException: Class
    org.apache.commons.logging.impl.Log4JLogger does not implement
    Log
        at javax.faces.webapp.FacesServlet
           .service(FacesServlet.java:2
    .....
    Caused by: 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(LogFactoryImp l.java:532)
        at org.apache.commons.logging.impl.LogFactoryImpl
           .getInstance(LogFactoryImp l.java:272)
        at org.apache.commons.logging.impl.LogFactoryImpl
           .getInstance(LogFactoryImp l.java:246)
        at org.apache.commons.logging.LogFactory
           .getLog(LogFactory.java:395)
        at org.apache.commons.beanutils.ConvertUtilsBean
           .<init>(ConvertUtilsBean.ja va:157)
        at org.apache.commons.beanutils.BeanUtilsBean
           .<init>(BeanUtilsBean.java:117 )
        at org.apache.commons.beanutils.BeanUtilsBean$1
           .initialValue(BeanUtilsBean. java:68)
        at org.apache.commons.beanutils.ContextClassLoaderLocal
           .get(ContextClassLoa derLocal.java:153)
        at org.apache.commons.beanutils.BeanUtilsBean
           .getInstance(BeanUtilsBean.jav a:80)
        at org.apache.commons.beanutils.PropertyUtilsBean
           .getInstance(PropertyUtils Bean.java:114)
        at org.apache.commons.beanutils.PropertyUtils
           .isReadable(PropertyUtils.java :652)
        at org.apache.myfaces.config.ManagedBeanBuilder
           .initializeProperties(Manage dBeanBuilder.java:267)
        at org.apache.myfaces.config.ManagedBeanBuilder
           .buildManagedBean(ManagedBea nBuilder.java:171)
        at org.apache.myfaces.el.unified.resolver
           .ManagedBeanResolver
           .createManaged Bean(ManagedBeanResolver.java:329)
        at org.apache.myfaces.el.unified.resolver
           .ManagedBeanResolver
           .getValue(Mana gedBeanResolver.java:292)
    

Local fix

  • none available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Full       *
    *                  Profile version 8.0 and 8.5.5 users of      *
    *                  JavaServer Faces(JSF) MyFaces 2.0.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications bundled with a             *
    *                      third-party JCL implementation can      *
    *                      conflict with the implementation        *
    *                      bundled with the server.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an application is bundled with a Jakarta Commons Logging
    (JCL) implementation, there can be a class loading conflict
    during the initialization of bean and converter properties.
    This is due to a conflict with the commons-logging
    implementation bundled with the server.
    There are two possible error scenarios that can occur
    depending on whether a bean or converter properties are being
    initialized. Either one or both error scenarios can occur.
    When initializing bean properties, an exception like the
    following can be thrown:
    Caused by:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException:
    org.apache.commons.logging.LogConfigurationException:
    Class org.apache.commons.logging.impl.Jdk14Logger does not
    implement Log
    at
    org.apache.commons.logging.impl.LogFactoryImpl.newInstance
    (LogFactoryImpl.java:532)
    at
    (org.apache.commons.logging.impl.LogFactoryImpl.getInstance
    LogFactoryImpl.java:272)
    at
    org.apache.commons.logging.impl.LogFactoryImpl.getInstance
    (LogFactoryImpl.java:246)
    at
    org.apache.commons.logging.LogFactory.getLog
    (LogFactory.java:395)
    at
    org.apache.commons.beanutils.ConvertUtilsBean.<init>
    (ConvertUtilsBean.java:157)
    at
    org.apache.commons.beanutils.BeanUtilsBean.<init>
    (BeanUtilsBean.java:117)
    at
    org.apache.commons.beanutils.BeanUtilsBean$1.initialValue
    (BeanUtilsBean.java:68)
    at
    org.apache.commons.beanutils.ContextClassLoaderLocal.get
    (ContextClassLoaderLocal.java:153)
    at
    org.apache.commons.beanutils.BeanUtilsBean.getInstance
    (BeanUtilsBean.java:80)
    at
    org.apache.commons.beanutils.PropertyUtilsBean.getInstance
    (PropertyUtilsBean.java:114)
    at
    org.apache.commons.beanutils.PropertyUtils.isReadable
    (PropertyUtils.java:652)
    at
    org.apache.myfaces.config.ManagedBeanBuilder.initializePropertie
    s(ManagedBeanBuilder.java:267)
    at
    org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean
    (ManagedBeanBuilder.java:171)
    ...
    An exception will not be thrown when initializing a
    converter's properties. Instead, an error similar to the
    following will be logged:
    ApplicationIm E   Initializing converter : <converter-class>
    with property : <propery-name> and value : <value> failed.
    

Problem conclusion

  • The JSF MyFaces code was updated to avoid a class loading
    conflict with application-provided JCL implementations when
    initializing bean or converter properties.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.12 and 8.5.5.9. 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

    PI47898

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-31

  • Closed date

    2015-09-30

  • Last modified date

    2015-09-30

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

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