MMapSessionManager (Unix Only)
Chapter 6 Session Managers 63
Parameters
MMapSessionManager takes the following parameters:
•
maxSessions - the maximum number of sessions maintained by the session
manager at any given time. The session manager refuses to create any more
new sessions if there are already
maxSessions number of sessions present at
that time. The default value is 1000.
•
maxValuesPerSession - the maximum number of values or objects a session
can hold. The default value is 10.
•
maxValueSize - the maximum size of each value or object that can be stored in
the session. The default value is 4096.
•
timeOut - the amount of time in seconds after a session is last accessed by the
client before the session manager destroys it. Those sessions that haven’t been
accessed for at least
timeOut seconds are destroyed by the reaper method. The
default value is 1800 (30 minutes).
If
session-timeout is specified in web.xml, it overrides this timeOut
parameter value. For details, see “session-timeout,” on page 15.
•
reapInterval - the amount of time in seconds that the SessionReaper thread
sleeps before calling the
reaper method again. The default value is 600 (10
minutes).
•
maxLocks - the number of cross-process locks to use for synchronizing access
to individual sessions across processes. The default value is 1. This default
value is used if the value 0 is specified. This parameter is ignored in
single-process mode.
Enabling MMapSessionManager
You may want to enable MMapSessionManager to change its default parameters.
You can also enable
MMapSessionManager for a particular context if the server is
running in single process mode. To enable iPlanet Web Server to use
MMapSessionManager, do any of the following:
• Use the Legacy Servlets>Configure Global Servlet Attributes page in the Server
Manager interface.
In the Session Manager field specify:
com.iplanet.server.http.session.MMapSessionManager
Kommentare zu diesen Handbüchern