Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Request to Prefix mapping of Faces servlet may return a 500 error.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile versions 8.0 and 8.5.5 and Liberty * * Profile version 8.5.5 users of JavaServer * * Faces (JSF) MyFaces 2.0. * **************************************************************** * PROBLEM DESCRIPTION: A request made to the prefix * * mapping of the Faces servlet will * * cause a loop that ends in a * * java.lang.NullPointerException. * **************************************************************** * RECOMMENDATION: * **************************************************************** Attempting to make a request to the prefix mapping of the Faces servlet without specifying a view is considered invalid because the JSP view definition language will dispatch to same URL. This causes a loop that ends in an exception. For example, if the Faces servlet mapping is /faces/*, making a request to /faces or /faces/ without a view will lead to a loop that has an execution path similar to the following: ... at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1230) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:779) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:478) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest (ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters (WebAppFilterManager.java:1114) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch( WebAppRequestDispatcher.java:1385) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(W ebAppRequestDispatcher.java:194) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.di spatch(ServletExternalContextImpl.java:367) at org.apache.myfaces.view.jsp.JspViewDeclarationLanguage.buildView (JspViewDeclarationLanguage.java:94) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(Rend erResponseExecutor.java:66) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl. java:240) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191) ... Eventually, this will lead to a java.lang.NullPointerException with a stack trace similar to the following: [java.lang.NullPointerException at org.apache.myfaces.shared_impl.context.flash.FlashImpl.isKeepMes sages(FlashImpl.java:394) at org.apache.myfaces.shared_impl.context.flash.FlashImpl._saveMess ages(FlashImpl.java:669) at org.apache.myfaces.shared_impl.context.flash.FlashImpl.doPostPha seActions(FlashImpl.java:275) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl. java:252) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:191)
Problem conclusion
The JSF MyFaces code was updated to throw a org.apache.myfaces.shared.application.InvalidViewIdException if a request is made to the prefix mapping of the Faces Servlet. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.11 and 8.5.5.6. 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
PI38066
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
2015-03-30
Closed date
2015-05-11
Last modified date
2015-05-11
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
Document Information
Modified date:
28 April 2022