eFix (APAR): PQ67476 
Status: testfix 

Release: WebSphere 4.0.2, 4.0.3, 4.0.4

Operating System: WindowsNT/2000

Supersedes eFixes: WAS_Plugin_10-18-2002_4.0.x_cumulative 

CMVC defect: PQ67476 

Byte size of APAR: 1,062,531

Date: 10/25/2002

Abstract: The plugin was setting the affinity cookie to use for determining session
          affinity whenever a uri matched the current url.  As a result we would use
          the affinity cookie from the last matched uri rather than the affinity
          cookie from the uri that determined the route. 
          This also fixes a separate problem where certain types of Uri definitions
          require the plugin to internally create another uri definition in order to correctly
          match.  As a result, if the original uri had a special affinity cookie set
          the new uri would not get updated with that affinity cookie.  If the new
          uri was the one matched, the wrong affinity cookie would be used.

Description/symptom of problem:  Session Affinity would not work when the user had
          multiple affinity cookies for the various applications they had installed.


Directions to apply efix:

1) Create temporary "efix" directory to store the jar file:
         Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown the web server.

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>
   NOTE: In a remote webserver environment where the full app server is not installed you
         will need to run the command with additional command line options in order for the
         install to work successfully:
         java -jar <jarfile name> -skipContainerCheck -dupCheck no -updateXML no

5) Restart the web server.

6) The temp directory may be removed but the jar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/PQ67476 directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/PQ67476).

2) Shutdown the web server.

3) Run the backup jar file with the following command:
   java -jar <backup_efix#>
   NOTE: In a remote webserver environment where the full app server is not installed you
         will need to run the command with additional command line options in order for the
         install to work successfully:
         java -jar <jarfile name> -skipContainerCheck -dupCheck no -updateXML no

4) Restart the web server.



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.



Additional Information:
------------------------------------------------------------------