PM68561: EJB CONTAINER FAILS TO RESTORE CONTEXT CLASSLOADER AFTER UNSUCCESSFUL DEFERRED BEAN INITIALIZATION

8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
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

• A deferred EJB is accessed, metadata initialization is
  successful, installation into the container fails, the deferred
  EJB is accessed again, metadata initialization is skipped since
  it was previously successful, and installation into the
  container fails again.  In this case, the EJB container fails
  to restore the context class loader
  

Local fix

• disabled deferred EJB initialization
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  V8.0 with an EJB that fails to start.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: EJB Container fails to restore          *
  *                      context classloader after failed bean   *
  *                      initialization                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  By default, the initialization of an EJB is deferred until
  first access. On first access, first the metadata for the bean
  is initialized and then the bean will be started in the
  container. If the metadata for the bean is initialized
  successfully, but the bean fails to start (some error occurs)
  then on the second attempt to access the bean, initialization
  is skipped, and the container will then fail to properly
  restore the context classloader after this second attempt to
  start the bean in the container.
  

Problem conclusion

• The EJB container has been updated to properly restore the
  context classloader after such an error scenario occurs.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP