PQ43061: SESSION AFFINITY DOES NOT WORK CORRECTLY.


APAR

APAR status
Closed as program error.

Error description
Session Affinity does not work correctly.
defect 87092
Local fix
Problem summary
affinity does not always work, both on WAS 3.5 GM and WAS 3.5
PTF 1. The client (browser) gets locked into a specific JVM on
the second request from the browser as advertised. However, it
seems like if second request from client gets WLMed to a JVM
other than the one it was created in, that JVM does not have
access to the HttpSession object, and no session is returned on
the session = request.getSession(false).
Problem conclusion
this problem:
ncf/src/native/ose/utils_lib/config.h
ncf/src/native/ose/utils_lib/config.c
ncf/src/native/ose/asout_lib/asoutc_lib/asout.c
this problem:ncf/src/native/ose/utils_lib/config.hncf/src/native/ose/utils_lib/config.cncf/src/native/ose/asout_lib/asoutc_lib/asout.c
Temporary fix
Comments
APAR information
APAR numberPQ43061
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2000-11-06
Closed date2000-11-17
Last modified date2001-12-17

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
PLUGIN
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R300 PSYUP
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ43061
IBM Group: Software Group
Modified date: 2001-12-17