Fix (APAR):  PK52621

Status:  Fix

Release:  6.0.2.19

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK52621

Byte size of APAR:  12880

Date: 2007-10-08

Abstract:  This scenario happens when an application is installed on 2 or more servers.  One of the applications is stopped.  Proxy still routes requests to the stopped server with the stoppe

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

ERROR DESCRIPTION:                                              
Logic problem in DWLM which causes an application to appear     
started by ODC even though it is not.  This can result in 404   
errors to the client as requests may be routed to inactive      
members                                                         

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
using a proxy server.

PROBLEM DESCRIPTION:
This scenario happens when an
application is installed on 2 or more
servers.  One of the applications is
stopped.  Proxy still routes requests
to the stopped server with the stopped
application. This results in the
application server issuing a 404 rather
than the request being properly routed
to an applcation server which can
handle it.

RECOMMENDATION:
None

The problem is that while the proxy has code to handle an
application that is stopped, there is a timing issue which
can potentially cause a null pointer exception, which will
then cause the application to not properly become listed as
stopped. There are alternative events which can be listened
to which are not affected by this potential null pointer. Proxy
needs to adjust what events are used to prompt listing an
application as stopped.

PROBLEM CONCLUSION:                                             
The code was fixed to listen to alternative events when keeping 
the state of an application, and the fix was made available for 
the 6.0.2 release. The fix will be included in Service Pack     
6.0.2.25 for WebSphere Application Server Network Deployment.   


Directions to apply fix:  
Fix applies to Editions:
Release 6.0
_x_ Network Deployment (ND)

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.
* Be at V6.0.2.2 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.

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 6.0.2.19-WS-WASND-IFPK52621.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.0.2.19-WS-WASND-IFPK52621.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 (6.0.2.19-WS-WASND-IFPK52621.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: