Fix (APAR):  PK22074

Status:  Fix

Release:  5.1.1.9

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  357358

Byte size of APAR:  3894

Date: 2006-04-06

Abstract:  beforeCompletion calls for Extended  JTA Transactions are in the wron g                               order.

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

ERROR DESCRIPTION:                                              
The following exception occurred when an attempt was made to    
write to a datasource, when in beforeCompletion() using the     
ExtendedJTATransaction support:                                 
[6/16/05 12:23:22:382 CDT] 00000047 ExceptionUtil E             
CNTR0019E: EJB threw an unexpected (non-declared) exception     
during invocation of method "create". Exception data:           
java.lang.IllegalStateException: Preparing                      
at com.ibm.ejs.container.ContainerTx.ensureActive               
     (ContainerTx.java:434)                                     
at com.ibm.ejs.container.ContainerTx.preInvoke                  
     (ContainerTx.java:1494)                                    
at com.ibm.ejs.container.EJSContainer.preInvokeActivate         
     (EJSContainer.java:3317)                                   
at com.ibm.ejs.container.EJSContainer.preInvoke                 
     (EJSContainer.java:2831)                                   

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server users of
Extended
JTATransactions

PROBLEM DESCRIPTION:
beforeCompletion calls for Extended

JTA Transactions are in the wron
g                               order.


RECOMMENDATION:
None



java.lang.IllegalStateException is thrown during
beforeCompletion processing. State is expected to be ACTIVE,
but as a result of ordering, it is set at PREPARING.

PROBLEM CONCLUSION:                                             
Changed order of synchronizations relating to Extended JTA      
Transactions in beforeCompletion().                             
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 5.1.1.11.  Please refer to the Recommended Updates      
page for delivery information:                                  
http://www.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:
5.0  5.1
___  ___ Application Server (Express or BASE)
___      Enterprise Edition (DD)
___  ___ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ 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.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

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

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar 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.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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.jar).

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: