Fix (APAR):  PM52188

Status:  Fix

Release:  6.1.0.5

Operating System:  AIX,Linux,Solaris,Windows

Supersedes Fixes:  PM33319, PM34779, PM35054, PM35274, PM35515, PM35900, PM36518, PM37059, PM37579, PM37856, PM37461, PM38880, PM39514, PM39989, PM40262, PM40426, PM40758, PM49565, PM50308, PM51859

CMVC Defect:  PM52188

Byte size of APAR:  37006502

Date: 2012-02-07

Abstract:  When using older versions of eXtreme Scale with version 7.1.1, you experience TargetNotAvailableException exceptions.

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

ERROR DESCRIPTION:?                                             
WebSphere eXtreme Scale Version 7.1.1.0 is not                  
compatible with container servers and clients that run          
older versions of WebSphere eXtreme Scale. This will prevent    
communication between older versions of eXtreme Scale and       
Version 7.1.1.0.                                                

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
 All users of WebSphere eXtreme Scale who
have mixed levels of the product or who
are upgrading to 7.1.1.0

PROBLEM DESCRIPTION:
When using older versions of eXtreme
Scale with version 7.1.1, you
experience
TargetNotAvailableException
exceptions.

RECOMMENDATION:
None

Thee client did not send the correct
information about its version. Therefore, the server was
expecting more data than was sent.  The problem was fixed and
an interim fix will be made available for previous releases to
7.1.1.
To determine if you are seeing this problem, enable trace with
the specification set to "ObjectGridRouting=all=enabled" on the
lower version client or container server. Trace should contain
several exceptions similar to the following example:
[11/14/11 9:26:46:515 CST]  6000600 ORBClientCore e
DefaultDomain:Grid:mapSet:12 Request bailed out with
connection problem.
org.omg.CORBA.MARSHAL:
>> SERVER (id=4f5d6e6c, host=9.10.86.157) TRACE START:
>>    org.omg.CORBA.MARSHAL: No available data: Request
34:read beyond end of data. No fragments available.  vmcid:
OMG  minor code: 8 completed: Maybe
>>  at
com.ibm.rmi.iiop.CDRReader.availableData(CDRReader.java:905)
>>  at
com.ibm.rmi.iiop.CDRReader.alignAndCheck(CDRReader.java:881)
>>  at
com.ibm.rmi.iiop.CDRInputStream.read_longlong(CDRInputStream.jav
a:376)
>>  at
com.ibm.ws.objectgrid.partition.RequestContextImpl.unmarshal(Req
uestContextImpl.java:126)
>>  at
com.ibm.rmi.iiop.CDRReader.read_value(CDRReader.java:2182)
>>  at
com.ibm.ws.objectgrid.partition.RequestContextDefaultFactory.rea
d_value(RequestContextDefaultFactory.java:15)
>>  at
com.ibm.rmi.iiop.CDRReader.readFactoryValue(CDRReader.java:2330)
>>  at
com.ibm.rmi.iiop.CDRReader.read_value(CDRReader.java:2262)
>>  at
com.ibm.ws.objectgrid.partition.RequestContextHelper.read(Reques
tContextHelper.java:71)
>>  at
com.ibm.ws.objectgrid.partition.IDLShardPOA._invoke(IDLShardPOA.
java:189)
Additionally you will see this same exception in FFDC on the
container server, if you have any interim fixes or fix
packs applied to the 7.1.1.0 product.

PROBLEM CONCLUSION:?                                            
Apply this fix to clients and container server installations    
prior to starting a rolling upgrade to the 7.1.1 release.       


Directions to apply fix:  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.
* 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

1) Copy the 6.1.0.5-WS-WXS-IFPM52188.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) Select the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Select the file name of the maintenance package to install ( the 6.1.0.5-WS-WXS-IFPM52188.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 Application Server.
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) Select the installation location of the WebSphere product you want to remove the fix.

4) Select "Uninstall maintenance package" operation.

5) Select the file name of the maintenance package to uninstall (6.1.0.5-WS-WXS-IFPM52188.pak).

6) UnInstall maintenance package.

7) Restart WebSphere



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

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.





Additional Information: