PQ57888: TWO SERVER REGIONS WITH SESSION.DBENABLE=FALSE NOT WORKING | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When customer has two server regions running, the session state data seems to be lost if the session is managed by a server other than the initial one that established the session. Customer has session.dbenable=false and would like to have the problem fixed instead of changing to session.dbenable=true.Local fix Change to session.dbenable=true.Problem summary **************************************************************** * USERS AFFECTED: Any WebSphere Application Server Version * * V4.0.1 for z/OS and OS/390 user attempting * * to save HTTP Session state in-memory while * * running multiple server regions under a * * single control region will experience * * apparent session data loss. * **************************************************************** * PROBLEM DESCRIPTION: Session data will intermittently be * * lost between HTTP requests. * **************************************************************** * RECOMMENDATION: * **************************************************************** When session data is stored in-memory, it cannot be shared across server regions. If a session is created in one server region, any request that gets routed to a different server region will not have access to the session data. A new session will be created in this server region, thus making it appear to the application that the initial session data has been lost. Internally, the data has not actually been lost, but it can no longer be accessed. Even if a subsequent request goes back to the original server region, the session ID provided by the client will be that of the new session, so the original session will eventually time out and the data will be invalidated.Problem conclusion With this new support, called Session Affinity, all requests specific to a particular session will be routed back to the server region where the session was created. This change affects COMPID 5655A9800 R401 for z/OS and OS/390. The code changes are stored in CMVC under defect PQ57888, 80388, and 80448. Documentation Change: A separate document, entitled "WebSphere Application Server V4.0.1 for z/OS and OS/390: Session Affinity" is available for this APAR. To download the document, go to the following Web site, then click "Product information." http://www-4.ibm.com/software/webservers/appserv/zos_os390 /support.html At a later time, the information in this document will be integrated into the WebSphere for z/OS formal publications. To access the latest publications, go to the product library page at: http://www-4.ibm.com/software/webservers/appserv/zos_os390 401Y EJSCASIN EJSCCLAS EJSCCMSV EJSCCNFG EJSCJNUT EJSCJNWR EJSCLOAD EJSCLOGR EJSCOEUT EJSCOSUT EJSCPLUG EJSCPLUT EJSCPOOL EJSCPROP EJSCRULS EJSCSTUB EJSCSVHS EJSCVALD EJSCVERS EJSCWSUT EJSJSVJR EJSJWBJR EJSJWCSC EJSJWCWC EJSJWC04 EJSLNLS EJSPWCNF EJSTLDAT EJSXASIN EJSXJVMX * Cross Reference between External and Internal NamesTemporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ57888
IBM Group: Software Group
Modified date: Apr 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.