Status:      This is a fix

For Release: WebSphere  4.0, 4.0.1

For Edition: WebSphere AE, AES, AED

For ContainerTypes: AEServer, AES, J2EE, ThinClient, All

For Operating System: ALL

Supersedes eFixes:  NONE

CMVC defect: PQ55940

Byte size of APAR: 846KB

Date: 12/17/01

Abstract: Session ID will be shared across WebApp's in a Multi-JVM environment without session persistence configured.

Description/symptom of problem: In a Multi-JVM environment without session persistence requests can be sent to different webapps. Since session persistence is not enabled the session manager cannot determine whether it is a valid session id or not if the session object does not exist in that JVM. This will cause a new session object to be created in the webapp's where this session object does not exist. With this fix, customers can use a system property called HttpSessionIdReuse which will make the session manager to use a sessionid sent from a browser.

Directions for applying the System Property on Advanced Edition Single Server :

1. Specify the System Property HttpSessionIdReuse = true
    Specifying the property using Administrative console.
    a. Under WebSphere Administrative Domain, Expand Nodes
    b. Expand Application Servers
    c. Expand Default Server
    d. Expand Process Definition
    e. Select JVM Settings, in the right hand panel under Advanced Settings, Click on System Properties.
    f. Click New button, Specify Name as HttpSessionIdReuse and Value as true. Click OK.
    g. Save the configuration changes.
2. Stop the Server
3. Start the Server.


Directions for applying the System Property on Advanced Edition :

1. Specify the System Property HttpSessionIdReuse = true
    Specifying the property using Administrative console.
    a. Under WebSphere Administrative Domain, Expand Nodes
    b. Expand Application Servers
    c. Select the Appserver( for example Default Server)
    d. Select JVM Settings, in the right hand panel under Advanced Settings.
    e. Click New button beside the table titled System Properties. Specify Name as HttpSessionIdReuse and Value as true. Click OK.
    f. Apply the configuration changes.
2. Stop the Server
3. Start the Server.



Directions to apply efix:

1) Create temporary "efix" directory to store the zip/tar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy zip/tar file to the directory
   
3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

6) Restart WebSphere

7) The temp directory may be removed but the zip/tar file should be saved.  Do not remove 
    any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<APAR#> 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/<APAR#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_APAR#>

4) Restart WebSphere


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.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file 
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix 
   and move the file back to it's original location.



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