PQ90221: OPTIMISTIC CONCURRENCY FAILURE RESULTS IN TRANSACTIONROLLEDBACK EXCEPTION, EJB CLIENT IS UNABLE TO HANDLE ORIGINAL EXCEPTION

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.1: WebSphere Application Server Express 5.1.1 Cumulative Fix 1
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.1.1.1: WebSphere Application Server Version 5.1.1 Cumulative Fix 1



APAR status
Closed as program error.

Error description
In WebSphere Application Server 5.0.x, a CMP entity bean is
configured with wsOptimisticUpdate access intent.  When two
users try to update the same row in the database simultaneously,
the following exception is thrown:
java.rmi.NoSuchObjectException:
com.ibm.ws.ejbpersistence.utilpm.OptimisticUpdateFailedException
:
PMGR6025E: An attempted update under optimistic concurrency
control failed because another application has changed the bean
data in the datastore since this transaction read it. Either it
changed a predicate field value or removed the bean itself.
.
and the transaction rolls back.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Enterprise Java Bean (EJB) developers who    *
*                 developing CMP2.0 Beans and are using        *
*                 Optimistic Concurrency.                      *
****************************************************************
* PROBLEM DESCRIPTION: Optimistic concurrency control          *
*                      failures are logged, but cannot         *
*                      handle them programatically.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An error such as "PMGR6025E: An attempted update under
optimistic concurrency control failed because another
application has changed the bean data in the datastore since
this transaction read it. Either it changed a predicate field
value or removed the bean itself." is logged. The client cannot
recover programmatically from it.
With this APAR, we will nest this exception for clients to
handle.
Problem conclusion
Modified code to allow nesting of
javax.ejb.NoSuchObjectLocalException as part of the exception
stack thrown back to the client.
Temporary fix
fixTest.jar mailed to customer.
Comments
APAR information
APAR number PQ90221
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-06-15
Closed date 2004-07-16
Last modified date 2005-01-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBCONTR          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ90221
IBM Group: Software Group
Modified date: Jan 27, 2005