IBM Support

PH09730: CLASSNOTFOUNDEXCEPTION OCCURRING DURING JSF INITIALIZATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the jsf-2.2 feature is enabled on 18.0.0.4 -
    application
    initialization is failing because of a
    ClassNotFoundException
    that occurs during JSF initialization.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of JavaServer Faces (JSF) in          *
    *                  WebSphere Application Server version 9.0    *
    *                  as                                          *
    *                  well as users of jsf-2.2 and jsf-2.3 in     *
    *                  WebSphere Liberty.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: JSF application initialization fails    *
    *                      when a servlet mapping is defined       *
    *                      which                                   *
    *                      cannot be loaded by JSF                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    JSF applications which define a servlet mapping that cannot
    be
    loaded by JSF will fail to initialize. A similar exception
    will
    be seen:
    javax.faces.FacesException:
    java.lang.ClassNotFoundException:
    <classname>
    at
    org.apache.myfaces.shared.util.ClassUtils.simpleClassForName
    (Cla
    ssUtils.java:239)
    at
    org.apache.myfaces.shared.util.ClassUtils.simpleClassForName
    (Cla
    ssUtils.java:215)
    at
    org.apache.myfaces.shared_impl.webapp.webxml.WebXml.getFaces
    Serv
    letMappings(WebXml.java:136)
    at
    org.apache.myfaces.spi.impl.DefaultWebConfigProvider.getFace
    sSer
    vletMappings(DefaultWebConfigProvider.java:46)
    at
    org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces
    (Abs
    tractFacesInitializer.java:161)
    

Problem conclusion

Temporary fix

  • Set the following web context parameter to "true" to skip
    the
    Faces Servlet mapping check which causes this initialization
    failure:
    org.apache.myfaces.INITIALIZE_ALWAYS_STANDALONE
    

Comments

APAR Information

  • APAR number

    PH09730

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-14

  • Closed date

    2019-04-02

  • Last modified date

    2019-05-29

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021