PI55574: HANDLERS START IN INCORRECT ORDER WHEN PROVISIONING IS ENABLED

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.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

• Handlers start in incorrect order when provisioning is enabled
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Modules are started in an incorrect     *
  *                      order when Application Server setting   *
  *                      "start components as needed" is         *
  *                      enabled.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For Java EE applications that contain an EJB within a WAR
  module, the application manager calls to containers to process
  that module in a specific order - first the EJB container,
  then the web container.  In environments with runtime
  provisioning (the "start components as needed" setting) and a
  set of applications that includes web-only application(s) in
  addition to the EJB-in-WAR application, it is possible for the
  EJB handler to be registered after the web handler, resulting
  in the module being processed incorrectly and potentially
  leading to failures when code in the WAR attempts to reference
  the EJB.
  

Problem conclusion

• Additional logic was added to handle this scenario and prevent
  out-of-order handler registration.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.11 and 9.0.0.2.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Disable the "start components as needed" setting on the
  failing Application Server.
  

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

• R850 PSY

     UP

• R900 PSY

     UP