PI68889: STARTUP BEAN INITIALIZATION FAILURE IS IGNORED WHEN CDI IS ACTIVE

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

• According to the EJB 3.1 specification, an application should
  not start when the initialization of a startup bean fails.
  We've noticed, however, when CDI is active, such initialization
  failure is silent and the application continues to start up
  and accept requests.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A EJB bean's initilization fails        *
  *                      without a warning                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When both EJB and CDI are enabled an EJB bean fails to
  initalize correctly and no warning is given in SystemOut.log
  

Problem conclusion

• Websphere Application Server's behaviour is correct according
  to the sepc. However it should give a warning when an EJB
  fails to initalize correctly so we removed unwanted restraints
  on when logging was emitted.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.11 and 8.0.0.13 .  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP