Fix (APAR):  PK28712

Status:  Fix

Release:  6.0.2.9,6.0.2.8,6.0.2.7,6.0.2.6,6.0.2.5,6.0.2.13,6.0.2.11

Operating System:  AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux,zSeries,Solaris,Windows

Supersedes Fixes:  NONE

CMVC Defect:  PK28712

Byte size of APAR:  16276

Date: 2006-09-03

Abstract:  When a CMP EJB insert or update fails and the transaction is rolled back, the per sistence 
manager may invoke an unnecessary update call to the CMP EJB.

Description/symptom of problem:  
PK28712 resolves the following problem:

ERROR DESCRIPTION:                                              
The APAR will address the defect in persistence manager that unnecessarily made an "UPDATE IDENTIFIER" 
call when a previous transaction is rolled back.                                     

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server version 6.0.2 and 6.1 users who use container managed bean persistence.


PROBLEM DESCRIPTION:
When a CMP EJB insert or update fails and the transaction is rolled back, the persistence manager may 
invoke an unnecessary update call to the CMP EJB in the next transaction.


RECOMMENDATION:
None



The persistence manager marks an EJB dirty after an attempt to update the EJB.  The EJB remains dirty 
after the transaction is rolled back.  Because of this, in the second transaction involving updates to 
the same EJB, an extra update call is made.  This is not desirable because: (1) extra database updates 
are costy and slow down performance; (2) it may result in violation of table integrity if it does not 
allow the specific type of update.

PROBLEM CONCLUSION:                                             
The persistence manager code has been updated to properly handle the clean up of dirty EJBs in a 
transaction rollback scenario.                                                       
                                                                
The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.17 and 6.1.0.4  

Please refer to the Recommended Updates page for delivery information:                          
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980 


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
_x_ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the 
Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PKxxxxx.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance 
that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the 
maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere



Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 
must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance 
that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).

6) UnInstall maintenance package.

7) Restart WebSphere



Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.



Additional Information:  The fix is applicable to 6.0.2.5 and up to 6.0.2.15.