Fix (APAR):  PK31999

Status:  Fix

Release:  5.1.1.9,5.1.1.8,5.1.1.7,5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3,5.1.1.2,5.1.1.11,5.1.1.10,5.1.1.1,5.1.1

Operating System:  AIX,Solaris

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  84344660

Date: 2006-10-03

Abstract:  Intermittent INV_OBJREF exceptions are  thrown

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

ERROR DESCRIPTION:                                              
Intermittent INV_OBJREF exceptions are thrown while             
accessing a Stateful session bean.  Any further invocations     
thereafter would fail.  The exception would start suddenly      
even though the same EJB calls work prior to this exception     

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server version 5.1.1
users.

PROBLEM DESCRIPTION:
Intermittent INV_OBJREF exceptions are

thrown

RECOMMENDATION:
None

Intermittent INV_OBJREF exceptions are thrown while
accessing a Stateful session bean.  Any further invocations
thereafter would fail.  The exception would start suddenly
even though the same EJB calls work prior to this exception.
The problem is caused due to a wrong stub being loded when
the EJB evacuation sequence happens.

PROBLEM CONCLUSION:                                             
The fix for this will be available in the 142 SR7 version       
of the JDK .                                                    

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: