APAR status
Closed as program error.
Error description
Under high multi-thread access to beans of a type with Lifetim
In Cache enabled, a findByPrimaryKey for key "a" will return
bean data for bean "z". This incorrect data could manifest
itself in a wide variety of external symptoms.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: This problem may affect customers who use *
* EJB CMP with DataCache option definition *
* other than OFF in WebSphere Application *
* Server 5.x. *
****************************************************************
* PROBLEM DESCRIPTION: The methods to access to the shared *
* object by concurrent threads were not *
* synchronized correctly. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Under high multi-thread access to beans of a type with Lifetime
In Cache enabled, a findByPrimaryKey for key "a" will return
bean data for bean "z". This incorrect data could manifest
itself in a wide variety of external symptoms. It has happened
for instance that what the submitter saw in his SPecJAppServer
application was a NullPointerException.
This defect has escaped detection so far apparently because
very high thread contention is necessary before it appears (the
window during which the thread collision can occur is very
small - but not zero) and only if lifetime in cache is turned
on for the bean under heavy use. The fix completely "closes"
this window of error.
Problem conclusion
Persistence Manager made the change to ensure the methods
to access to the shared object by concurrent threads are
synchronized correctly.
Temporary fix
The fix was tested and the code checked in CMVC
Comments
APAR information |
APAR number |
PQ86337 |
Reported component name |
WAS STANDARD NT |
Reported component ID |
5648C8301 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-18 |
Closed date |
2004-05-06 |
Last modified date |
2004-05-07 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
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 |
|