PQ73028: USING WSOPTINMISTICE UPDATE, GET EXCEPTION COM.IBM.WS.EJBPERSISTENCE.UTILPM.OPTIMISTICUPDATEFAILEDEXCEPTION:PMGR6025E

 A fix is available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)



APAR status
Closed as program error.

Error description
With access intent on the Entity is wsOptimistic update for all
all fields are not-nullable and all (excepting the primary key o
course) are included in the Optimistic Predicate WHERE clause.
Exception is
ExceptionUtil E CNTR0021E:
Non-application exception occurred on bean
"BeanId(BeanName#jmsmessageEJB.jar#JMSMessage, 87010)": Exceptio
n data: java.rmi.NoSuchObjectException:
com.ibm.ws.ejbpersistence.utilpm.OptimisticUpdateFailedException
PMGR6025E:
An attempted update under optimistic concurrency control failed
another application has changed the bean data in the datastore s
this
transaction read it. Either it changed a predicate field value o
removed the bean itself.
   at
com.ibm.ejs.container.ContainerManaged2_0BeanO.store(ContainerMa
BeanO.java:237)
   at
com.ibm.ejs.container.EntityBeanO.beforeCompletion(EntityBeanO.j
)
   at
com.ibm.ejs.container.ContainerTx.beforeCompletion(ContainerTx.j
iledCode))
   at
com.ibm.ejs.util.tran.SyncDriver.beforeCompletion(SyncDriver.jav
   at
com.ibm.ejs.jts.jta.TransactionImpl$SyncronizationWrapper.before
ion(TransactionImpl.java:1233)
Local fix
Internal defect 155147 fixes problem.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of CMP    *
*                 Enterprise Java Beans.                       *
****************************************************************
* PROBLEM DESCRIPTION: When using CMP EJBs with multiple       *
*                      threads (clients), if each bean         *
*                      performs an update some data may be     *
*                      lost.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This APAR fixes a problem that occurs when mutiple beans are
used (on multiple threads), and attempt to update the Database
simultaneously.  The same interaction spec was used for each
thread, which resulted in only one set of updates being
committed to the DataBase.
Problem conclusion
Modified RRA code to use separate interaction specs.
Temporary fix Comments
APAR information
APAR number PQ73028
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-04-09
Closed date 2003-04-28
Last modified date 2003-04-28

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
RRA          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ73028
IBM Group: Software Group
Modified date: Apr 28, 2003