PI26908: ERROR PAGE HANDLING IS BROKEN WHEN THE WEB APPLICATION IS CDI ENABLED.

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• Error page handling is broken when the web application is CDI
  enabled.
  
  WebSphere Application Server 8.5.0.
  Distributed Operating Systems.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Full       *
  *                  Profile versions 8.5.5, and Liberty         *
  *                  Profile version 8.5.5 users of              *
  *                  WebContainer and Contexts and Dependency    *
  *                  Injection (CDI).                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: A                                       *
  *                      ContextNotActiveException might be      *
  *                      seen when an error page uses CDI and    *
  *                      a request is made to a non-existing     *
  *                      resource.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A javax.enterprise.context.ContextNotActiveException might be
  seen when CDI annotations are used on a custom error page and
  a request is made to a resource that does not exist. The
  exception prevents the error page from displaying correctly.
  The following is an example of the stack trace that might be
  seen:
  javax.enterprise.context.ContextNotActiveException: WebBeans
  context with scope type annotation @RequestScoped does not
  exist within current thread
  at
  org.apache.webbeans.container.BeanManagerImpl.getContext(BeanMan
  agerImpl.java:342)
  at
  org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler
  .getContextualCreationalContext(NormalScopedBeanInterceptorHandl
  er.java:169)
  at
  org.apache.webbeans.web.intercept.RequestScopedBeanInterceptorHa
  ndler.getContextualInstance(RequestScopedBeanInterceptorHandler.
  java:79)
  at
  org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler
  .invoke(NormalScopedBeanInterceptorHandler.java:114)
  at
  org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler
  .invoke(NormalScopedBeanInterceptorHandler.java:108)
  at
  org.apache.webbeans.conversation.ConversationImpl_$$_javassist_0
  .isTransient(ConversationImpl_$$_javassist_0.java)
  at
  org.apache.webbeans.jsf.WebBeansPhaseListener.beforePhase(WebBea
  nsPhaseListener.java:106)
  at
  org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseLis
  tenersBefore(PhaseListenerManager.java:76)
  at
  org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(Lifecycl
  eImpl.java:160)
  at
  org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl
  .java:119)
  at
  javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
  at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
  apper.java:1282)
  at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
  vletWrapper.java:802)
  

Problem conclusion

• The WebContainer code was modified to fix the exception and
  display the error page correctly.
  
  
  A new WebContainer custom property needs to be set to enable
  the behavior provided by this APAR:
  
  Name:
  com.ibm.ws.webcontainer.deferServletRequestListenerDestroyOnErro
  r
  
  Values: true/ false (default)
  
  
  Please refer to the following technote for instructions on
  enabling WebContainer custom properties:
  
  Full profile:
  http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395
  
  Liberty profile:
  http://www-01.ibm.com/support/docview.wss?uid=swg21597753
  
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 8.5.5.5.
  
  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 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

• R850 PSY

     UP