PM38857: ACCESSING A STATFUL SESSION BEAN MULTIPLE TIMES WITHIN THE SAME TRANSACTION CONTEXT MAY RESULT IN A HANG CONDITION.

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
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

• When accessing the same stateful session bean instance multiple
  times within the same transaction context, a hang condition may
  occur.
  
  This condition may occur for stateful beans configured with
  container managed transactions where remote interfaces are used.
  
  
  This may also occur for stateful beans configured with bean
  managed persistence and a global transaction is started
  within the scope of one method call, but not completed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  V8.0 with applications that may             *
  *                  concurrently  access Stateful Session       *
  *                  Enterprise Java Beans.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Accessing the same stateful session     *
  *                      bean multiple times within the same     *
  *                      transaction context, a hang condition   *
  *                      may occur.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In prior releases, any attempt to concurrently access a
  stateful bean instance would result in an exception (either
  BeanNotReentrantException or ConcurrentAccessException). With
  WebSphere Applicaiton Server V8, access is now blocked until
  the current thread accessing the bean completes, however there
  have been some scenarios where this may result in a thread
  being blocked indefinitely.
  

Problem conclusion

• Corrections have been made to the stateful session bean state
  management and concurrency locking to correct the hang
  conditions. Concurrently accessing stateful bean instances
  will no longer result in hang conditions.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.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