IBM Support

PH01566: MYFACES 2.1 BUG THE LOOKS LIKE IT MAY BE PAR OF THE IBM 2.2 HTTPS://ISSUES.APACHE.ORG/JIRA/BROWSE/MYFACES-3629

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

Local fix

  • As temporary workaround for the customer, setting this web
    context parameter in applications with faces servlet
    web-fragments will allow the applications to start up correctly:
    
        <context-param>
    
    
    <param-name>org.apache.myfaces.INITIALIZE_ALWAYS_STANDALONE</par
    am-name>
    
           <param-value>true</param-value>
    
         </context-param>
    
    
    
    Documentation for this parameter:
    
    https://myfaces.apache.org/core22/myfaces-impl/webconfig.html#?o
    rg_apache_myfaces_INITIALIZE_ALWAYS_STANDALONE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of JavaServer Faces (JSF) in          *
    *                  WebSphere Application Server version 9.0    *
    *                  as well as users of jsf-2.3 in WebSphere    *
    *                  Liberty.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: JSF application initialization fails    *
    *                      if the Faces Servlet mapping is only    *
    *                      defined in a web-fragment.xml           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Applications that only define a Faces Servlet mapping in a
    web-fragment.xml will fail to initialize.  A similar exception
    will be seen:
    "Caused by: java.lang.IllegalStateException: No Factories
    configured for this Application. This happens if the
    faces-initialization does not work at all - make sure that you
    properly include all configuration settings necessary for a
    basic faces application and that all the necessary libs are
    included. Also check the logging output of your web
    application and your container for any exceptions!
    If you did that and find nothing, the mistake might be due to
    the fact that you use some special web-containers which do not
    support registering context-listeners via TLD files and a
    context listener is not setup in your web.xml.
    A typical config looks like this;
    <listener>
    <listener-
    class>org.apache.myfaces.webapp.StartupServletContextL
    istener</listener-class>
    </listener>
    at
    javax.faces.FactoryFinder._getFactory(FactoryFinder.java:310)
    at
    javax.faces.FactoryFinder.getFactory(FactoryFinder.java:230)
    at
    javax.faces.webapp.FacesServlet.init(FacesServlet.java:121)
    at
    com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapp
    er.java:297)
    ... 15 more"
    Note that this exception indicates a general JSF
    initialization failure, and not necessarily the issue resolved
    by this APAR.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH01566

  • 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

    2018-08-10

  • Closed date

    2018-10-15

  • Last modified date

    2019-04-09

  • 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

  • R900 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":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021