PK64612: DATACACHE ENTRIES NOT EVICTED WHEN MULTIPLE OPTLOCKEXCEPTIONS ARE RETURNED BY THE DATABASE

APAR status

• Closed as program error.

Error description

• DataCache entries not evicted when multiple OptLockExceptions
  are returned by the database.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of ibm WebSphere Application      *
  *                  Server Feature Pack for EJB 3.0 with        *
  *                  DataCache enabled.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: DataCache entries not evicted when      *
  *                      multiple OptimisticLockExceptions are   *
  *                      returned by the database.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application is working on an instance of an entity
  which is outdated with respect to database (that is, it uses
  stale data) and requests an update, the update is supposed to
  get an OptimisticLockException. However after receiving an
  SQLException from the database, an OptimisticLockException is
  not thrown to the application. This causes the application to
  assume that the update was successful, but in reality it is not
  the case. The application continues to use the stale data.
  

Problem conclusion

• The logic is corrected to assure the following steps are taken:
  1. Received SQLException is propagated as
  OptimisticLockException,
  2. DataCacheManager detects that the OptimisticLockExcpetion
  occurred and evicts the stale object in the cache.
  3. The transaction is rolled back.
  4. Application gets PersistenceException.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.19.  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

  WAS EJB3 FEATUR

• Fixed component ID

  5724J0851

Applicable component levels

• R610 PSY

     UP