Fix (APAR):  PM29366

Status:  Fix

Release:  6.1.0.5

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

Supersedes Fixes:  

CMVC Defect:  PM29366

Byte size of APAR:  111370

Date: 2011-01-25

Abstract:  The xsadmin -routetable command runs in the catalog server process.

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

ERROR DESCRIPTION:?                                             
The xsadmin -routetable command sends a simple request to every 
shard in the grid to validate the route table information in the
catalog is consistent with the state of the grid itself. This   
was implemented in the catalog server such that it was the      
catalog itself that was doing all of this work.  This action    
causes more a long running operation in the catalog service that
could not be preempted. Each issuance of the command consumes   
another thread in the catalog server.                           
                                                                
It is preferable to have the xsadmin process itself contain the 
responsibility of calling each of the shards.  This fix moves   
this logic into the command to remove impact on the catalog     
server.                                                         

LOCAL FIX:?                                                     
N/A                                                             

PROBLEM SUMMARY:?

USERS AFFECTED:
 All users of WebSphere eXtreme Scale.

PROBLEM DESCRIPTION:
The xsadmin -routetable command runs in
the catalog server process.

RECOMMENDATION:
None

The xsadmin -routetable command might hang and be
unresponsive.

PROBLEM CONCLUSION:?                                            
The xsadmin -routetable command was updated  to run in the      
client Java virtual machine (JVM) instead of the catalog server 
JVM.                                                            
                                                                
A future cumulative fix corrects the problem for WebSphere      
eXtreme Scale Versions 7.0 and 7.1.                             


Directions to apply fix:  Install Fix to:

__ 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. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix 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.

Customers must be at V6.1.0.17 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.

1) Copy 6.1.0.5-WS-WXDOG-IFPM29366.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 (6.1.0.5-WS-WXDOG-IFPM29366.pak 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.

NOTE:  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 (6.1.0.5-WS-WXDOG-IFPM29366.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: