Fix (APAR):  PM06349

Status:  Fix

Release:  6.1.1

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

Supersedes Fixes:  PK99664;PM04611;PM05220

CMVC Defect:  PM06349

Byte size of APAR:  486954

Date: 2010-02-10

Abstract:  The on demand router (ODR) returns 503 HTTP errors for applications that use alternate deployment descriptors.

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

ERROR DESCRIPTION:                                              
ODR returns 503s for applications utilizing alternate deployment
descriptors.                                                    

LOCAL FIX:                                                      
n/a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Virtual Enterprise
Version 6.1.1 who are making use of
alternate deployment descriptors within
applications

PROBLEM DESCRIPTION:
The on demand router (ODR) returns 503
HTTP errors for applications that use
alternate deployment descriptors.

RECOMMENDATION:
None

As applications that use alternate deployment descriptors
are starting, the callbacks the on demand configuration (ODC)
relies on for notification of which Web modules are running in
the server return the relative location to the alternate
descriptor rather than the URI of the Web module. As a result,
the ODC does not reflect the true running state of the Web
modules, and the ODR returns 503 errors for the application.

PROBLEM CONCLUSION:                                             
This error was fixed by introducing a new callback API that     
always returns the Web module URI during the start of an        
application so that the ODC correctly reflects the current      
state of the environment. PM06357: ADD GETMODULENAME TO         
DEPLOYEDMODULE must be installed in conjunction with this APAR  
to fully address this issue.                                    


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 PM06349.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 (PM06349.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 (PM06349.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: