PI15385: EJB CONTAINER LOCKS AND DOES NOT UNLOCK AN OBJECT.

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

• The problem appears to be a programming error in the ejb
  container code whereby the ejb container locks an Object and
  never unlocks it - it seems related to an exception case where
  the exception is generated by the ejb container code itself.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 with Enterprise Java Beans      *
  *                  applications that use stateful session      *
  *                  beans.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application hang occurs attempting      *
  *                      to call stateful session bean.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a call to a stateful session bean fails because the
  stateful bean is already active in another transaction (which
  may be a normal/expected failure), then the WebSphere
  Application Server does not properly release locks obtained
  for the stateful bean instance, resulting in later attempts by
  the application to use the bean hanging.
  When this condition occurs, an exception similar to this will
  be present:
  StatefulSessi 1   atActivation: exception raised
  com.ibm.ejs.container.BeanNotReentrantException:
  TX_METHOD_READY: wrong transaction
  at
  com.ibm.ejs.container.CMStatefulBeanO.enlist(CMStatefulBeanO.jav
  a:205)
  at
  com.ibm.ejs.container.activator.StatefulSessionActivationStrateg
  y.atActivate(StatefulSessionActivationStrategy.java:473)
  

Problem conclusion

• The WebSphere Application Server EJB container has been
  updated to properly release locking for stateful session beans
  when a failure occurs calling a method on the stateful session
  bean due to concurrent access. Later attempts to use the
  stateful bean will work properly.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.10.  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