Nessessionmanager; Parameters For Nessessionmanager - Netscape ENTERPRISE SERVER 6.1 - PROGRAMMER GUIDE TO SERVLETS Programmer's Manual

Guide to servlets
Table of Contents

Advertisement

NESSessionManager

NESSessionManager
The
NESSessionManager
NESSessionManager
be used for sharing session information across multiple processes possibly running
on different machines. The
whether the server is running in single process mode or multi-process mode. For
more information, see the Netscape Enterprise Server NSAPI Programmer's Guide.
For session persistence,
file system (DFS) path that is accessible from all servers in a server farm. Each
session is serialized to the database or distributed file system. You can also create
your own persistence mechanism.
If Enterprise Server is running in single-process mode, then by default, no session
persistence mode is defined and therefore sessions are not persistent.
If Enterprise Server is running in multi-process mode, sessions are persistent by
default. If a persistence mode is not defined,
Multi-process mode is supported only on UNIX platforms. All multi-process mode
features of

Parameters for NESSessionManager

NESSessionManager
maxSessions
manager at any given time. The session manager refuses to create any more
new sessions if there are already
that time. The default value is 1000.
timeOut
before the session manager destroys it. Those sessions that haven't been
accessed for at least
default value is 1800 (30 minutes).
If
parameter value. For details, see "session-timeout," on page 15.
reapInterval
sleeps before calling the
minutes).
58
Netscape Enterprise Server Programmer's Guide to Servlets • April 2002 (Draft)
is the default session manager.
works in both single process and multi-process mode. It can
NESSessionManager
NESSessionManager
takes the following parameters:
- the maximum number of sessions maintained by the session
- the amount of time in seconds after a session is accessed by the client
timeOut
is specified in
session-timeout
- the amount of time in seconds that the
directive in the
MaxProcs
can use a database or a distributed
NESSessionManager
are ignored on Windows NT/Windows 2000.
maxSessions
seconds are destroyed by the
, it overrides this
web.xml
method again. The default value is 600 (10
reaper
file determines
magnus.conf
uses a DFS.
number of sessions present at
method. The
reaper
timeOut
SessionReaper
thread

Advertisement

Table of Contents
loading

This manual is also suitable for:

Enterprise server 6.1

Table of Contents