Fix (APAR):  PK77267

Status:  Fix

Release:  6.0

Operating System:  AIX, Windows, Linux, Solaris, HP-UX

Supersedes Fixes:  

CMVC Defect:  PK77267

Byte size of APAR:

 91,500,306 6.0.0.X-WS-WASJavaSDK-AixPPC32-IFPK77267.pak
101,952,389 6.0.0.X-WS-WASJavaSDK-HpuxPaRISC-IFPK77267.pak
127,275,151 6.0.0.X-WS-WASJavaSDK-LinuxPPC32-IFPK77267.pak
107,311,817 6.0.0.X-WS-WASJavaSDK-LinuxS390-IFPK77267.pak
119,858,134 6.0.0.X-WS-WASJavaSDK-LinuxX32-IFPK77267.pak
 81,163,639 6.0.0.X-WS-WASJavaSDK-SolarisSparc-IFPK77267.pak
114,806,910 6.0.0.X-WS-WASJavaSDK-WinX32-IFPK77267.pak
 60,412,446 6.0.1.X-WS-WASJavaSDK-HpuxIA64-IFPK77267.pak
 77,147,098 6.0.1.X-WS-WASJavaSDK-LinuxIA64-IFPK77267.pak
 61,984,716 6.0.1.X-WS-WASJavaSDK-LinuxPPC64-IFPK77267.pak
 54,249,384 6.0.1.X-WS-WASJavaSDK-WinIA64-IFPK77267.pak
 46,923,782 6.0.2.X-WS-WASJavaSDK-AixPPC64-IFPK77267.pak
 53,493,868 6.0.2.X-WS-WASJavaSDK-LinuxS390_64-IFPK77267.pak
 45,850,770 6.0.2.X-WS-WASJavaSDK-SolarisAMD64-IFPK77267.pak

Date: 2008-12-17

Abstract: *ORB* meta calls with COM.IBM.CORBA.ENABLECLIENTCALLBACK=TRUE fails sometimes

ERROR DESCRIPTION:                                              
Error Message: With com.ibm.CORBA.enableClientCallback=true and 
fragmentation on, some requests fail when the request id of the 
meta operation is the same as the initial request for which the 
meta callback was triggered.                                    
.                                                               
Stack Trace: org.omg.CORBA.MARSHAL: No available data: Request  
8:read beyond end of data. No fragments available. vmcid: OMG   
minor code: 8 completed: Maybe                                  
at                                                              
com.ibm.rmi.iiop.CDRInputStream.alignAndCheck(CDRInputStream.jav
a:619)                                                          
at                                                              
com.ibm.rmi.iiop.CDRInputStream.alignAndCheck(CDRInputStream.jav
a:539)                                                          
...                                                             
at                                                              
com.ibm.rmi.io.ValueHandlerImpl.readValue(ValueHandlerImpl.java:
200)                                                            
at                                                              
com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:1
986)                                                            

LOCAL FIX: 
1)set com.ibm.CORBA.enableClientCallback=false on the side to which the meta call is triggered                                
2)set com.ibm.CORBA.FragmentSize to 0 (ie fragmentation switched off) or to be larger than the largest GIOP message              

USERS AFFECTED:
IBM WebSphere Application Server Version 6.0 users at SR10. Please NOTE this apar fix is for SR10 ONLY. 
Applying this apar fix PK77267 to SDK SR9 or lower will upgrade your SDK to SR10 plus this apar fix. 
Applying this apar fix PK77267 to SDK SR11 or higher will downgrade your SDK to SR10 plus this apar fix. 

Directions to apply fix:  
Use the latest Update Installer to install this Apar:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

Fix applies to Editions:
IBM WebSphere Application Server V6.0.x
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
_x_ WebSphere Business Integration Server Foundation (WBISF)
_x_ Edge Components
_x_ Developer
_x_ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
_x_ 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.
* Use the latest 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 .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 (.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 (.pak file name).

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: