PM62774: CDI POSTCONSTRUCT INJECTION DOES NOT WORK IN @STARTUP EJBS

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Contexts and Dependency Injection (CDI) constructor injection
  DOES NOT work in @Startup EJBs
  
  OWB keys its various services by classloader. All EJBs in an ear
  share the same classloader, so to make things work we do not
  start the CDI contexts or provide bean information until all ejb
  modules have started (basically when the ear finishes startup).
  To do so any earlier would mean we would only have partial
  information about the EJBs & classes in those services.
  
  Effectively that means we can not provide injection into
  @Startup EJBs, because they start when the individual EJB
  modules start and none of the OWB services are started yet. The
  CDI 1.0 spec itself doesn't talk about @Startup EJB and how that
  affects life cycles, which is why this is a bit of a grey area.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server version 8  *
  *                  users of CDI with EJB.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: @Singleton @Startup EJBs that reference *
  *                      a                                       *
  *                      CDI injected object in an               *
  *                      @PostConstruct                          *
  *                      method will fail.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The CDI Container starts its lifecycle too late during the
  startup of an application to be active when the PostConstruct
  method of an @Singleton @Startup ejb is run, leading to a null
  BeanManager and inactive scopes.
  

Problem conclusion

• A JVM property "com.ibm.ws.cdi.immediate.ejb.start" has been
  introduced that defaults to false.  When this property is set
  to true, the CDI container and its lifecycles will start for
  all EJB modules as soon as the application begins to start.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.4 and 8.5.0.1.  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

• R800 PSY

     UP

• R850 PSY

     UP