Fix (APAR):  PM44418

Status:  Fix

Release:  6.1.1.4,6.1.1.3,6.1.1.2,6.1.1

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

Supersedes Fixes:  PK99664;PM04611;PM05220;PM06349;PM07037;PM08969;PM11582;PM11623;PM12939;PM18326;PM22866;PM25095;PM30114;PM31735;PM31801;PM33050;PM33283;PM36464

CMVC Defect:  xxxxxx

Byte size of APAR:  509358

Date: 2011-10-31

Abstract:  On-Demand Routers incorrectly return 503s for requests destined for non-WebSphere processes managed by standalone agents.

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

ERROR DESCRIPTION:                                              
ODC reflects incorrect nonWAS middleware server states. This    
shows up when the ODR does not assign a request the IHS after   
the NodeAgent/Appserver/IHS are restarted.                      

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 Users of WebSphere Virtual Enterprise
v6.1.1 using standalone agent
functionality to manage non-WebSphere
middleware servers.

PROBLEM DESCRIPTION:
On-Demand Routers incorrectly return
503s for requests destined for
non-WebSphere processes managed
by standalone agents.

RECOMMENDATION:
None

After restarting standalone agents (xdagents), the On-Demand
Configuration (ODC) tree can incorrectly mark middleware
servers that are managed by the xdagents as stopped when they
are actually started. This results in On Demand Routers
returning 503 error codes for requests that are destined for
these middleware servers rather than servicing them correctly.

PROBLEM CONCLUSION:                                             
The ODC start-up logic on xdagents has been corrected to avoid  
the possibility of incorrectly marking middleware servers       
managed by the xdagent as stopped when the middleware servers   
are in actuality running.                                       
                                                                
This fix will be included in the next available fix pack for    
WebSphere Virtual Enterprise.                                   


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.1.0-WS-WXD-IFPM44418.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.1.0-WS-WXD-IFPM44418.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.1.0-WS-WXD-IFPM44418.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: