PQ55686: SESSION CONFIGURATION WAS PICKED UP FROM AN SESSION.XML FILE INSTEAD OF FROM THE DATABASE


APAR

APAR status
Closed as program error.

Error description
session configuration was picked up from an session.xml file
instead of from the database
.
The Appserver is started and very soon after starting it, a
 HttpRequest for a HttpSession is made. Since the SessionManager
 hasn't been initialized yet we make the request to wait for a
 minute until WebSphere(ManagedServer) gets to the task of
 initializing it. Normally, one minute is sufficient but in this
 customer's case WebSphere does not get to the task of initializ
the Session Manager until two and half minutes after WebSphere
started. After one minute has elapsed the servlet engine attempt
 to initialize the SessionManager on its own and reads the
 sessions.xml file  found in the properties directory.
Local fix
Re-naming(removing )  session.xml under
 websphere-root/properties
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server - HTTPSession   *
*                 Users                                        *
****************************************************************
* PROBLEM DESCRIPTION: The session configuration was being     *
*                      picked up from the sessions.xml file    *
*                      by the session manager after one        *
*                      minute had elapsed.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the AppServer is initializing and a web request comes in
for a HttpSession and the session configuration has not yet
been loaded from the database, the servlet engine waits for a
minute before attempting to initialize the session manager
from the sessions.xml file. In most cases, this time interval
which is hardcoded is enough.  However, there may be cases
where it might take longer for the session manager to
initialize from the database. For such cases a system property
is being provided which can be used to make the servlet engine
wait for a longer time.
Problem conclusion
A system property called SessionConfigInit can be set to
configure the amount of time which the servlet engine would
wait to allow the session configuration to be read from the
database.  This will override the default value of 60s which is
hardcoded in the session manager.  The value which can be set
will be in seconds.
Temporary fix
PQ55686
Comments
APAR information
APAR numberPQ55686
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-12-10
Closed date2002-01-03
Last modified date2002-01-03

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
SESSION
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
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ55686
IBM Group: Software Group
Modified date: 2002-01-03