PI30964: EJBS CONFLICTING WITH LISTENER CONFIGURATION AND CDI EVENTS

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

• Exception:
  
  [2014-11-17 08:46:28:023 CET] 00000025 id=
  com.ibm.ws.webcontainer.webapp.WebApp E
  notifyServletContextCreated SRVE0283E: Exception caught while
  initializing context:
  javax.enterprise.context.ContextNotActiveException: WebBeans
  context with scope type annotation @ApplicationScoped does not
  exist within current thread
   at
  org.apache.webbeans.container.BeanManagerImpl.getContext(BeanMan
  ager
   at
  org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler
  .get
   at
  org.apache.webbeans.intercept.ApplicationScopedBeanInterceptorHa
  ndle
  
  
  Is similar to APAR PI19074
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile - Contexts and       *
  *                  Dependency Injection (CDI)                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: EJBs conflicting with listener          *
  *                      configuration and CDI clients           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When listeners for ServletContext events and ServletRequest
  events were coded to inject Application Scoped CDI beans it was
  found that while the beans behaved as expected when the Ejblite
  feature was configured they were out of application scope when
  the Ejblite feature was added to the configuration.
  

Problem conclusion

• The CDI application context needed to be made available to
  threads other than the thread on which the context was initially
  created.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP