NonStop Servlets for JavaServer Pages (NSJSP) 5.0 System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-003
3-51
Configuring the Manager for Sessions Support
checkInterval
The number of seconds between checks for expired sessions. The default value
used is 60 seconds.
debug
The debug level for messages logged to the associated <Logger>. Higher
numbers generate more detailed output. The default is 0 (zero).
entropy
A string value used when seeding the random-number generator that creates
session identifiers. If this attribute is not specified, a preset value is used. For a
security-conscious environment, use a long string value.
maxActiveSessions
The maximum number of active sessions that can be created. The default is -1 for
no limit or unlimited active sessions.
randomClass
The Java class name of the java.util.random implementation class. The
default class is java.security.SecureRandom.
Example 3-35 shows how to use the NSJSPStandardManager.
NSJSPPersistentManager (Session Persistence Support)
NSJSPPersistentManager is the persistent implementation of a session manager. It
can swap active, but idle, sessions out to a persistent store, as well as save sessions
across restarts of the NSJSP container. The actual persistent store mechanism is
configured through a <Store> element nested under the <Manager> element.
In addition to the attributes specified in Configuring the Manager for Sessions Support
on page 3-49, NSJSPPersistentManager supports these attributes:
Example 3-35. Using the NSJSPStandardManager
<Context path="/servlet_jsp/myapp" docbase="myapp" reloadable="false"
debug="0" >
<!- Using the default NSJSPStandardManager but with a check
Interval time of 5 minutes (300 secs) instead of the default 60
seconds and also changed the entropy attribute for security
reasons.
-->
<Manager
className="com.tandem.servlet.catalina.session.NSJSPStandardManager"
debug="0" checkInterval="300"
entropy="hp NonStop™ Enterprise Division" />
</Context>
Note. To provide persistent sessions support, configure a <Store> element.