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

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide—544548-004
3-6
servlet.config
-DSaveSessionOnCreation=[ true | false ]
Enables or disables saving sessions into a persistent store during creation
time.
The default value is false. This is to prevent saving the session before it is
modified by the user application. This also reduces the database operation for
every client request.
If both SaveSessionOnCreation and
SessionBasedLoadBalancing options are set to false, and if a persistent
manager is configured with a persistent store, then all sessions are written to
the store at the end of each request processing cycle. As a result, all changes
made to the session by the user application are persisted to the store.
-DSessionBasedLoadBalancing=[ true | false ]
Enables or disables session-based load balancing. The default value is true.
When set to false and a Persistent Manager is configured with a persistent
store, sessions are written to the store at the end of each request processing
cycle. As a result, all changes made to a session by the client application are
persisted to the store.
-DSessionBasedCookieExpiry=[ true | false ]
Controls the expiration time of session cookies. The default value is false,
which means that the session cookie will be alive as long as the browser is
alive. If it is set to true, the session cookie will have the same expiration time
as that of the session.
-DDiscardFileMapHistory=[ true | false ]
Preserves or discards the history of all Filemap-related changes.
The default value is false, which means that the history of Filemap-related
changes, made during the lifecycle of the server, is preserved.
-DEnableJMXProxyServlet=[ true | false ]
This argument is not valid in NSJSP 6.0 because the proxy servlet can be
enabled or disabled in the web.xml file in the NSJSP Manager application.
Note. If the session timeout value is low (the default duration is thirty minutes) and
the clock values on the server and client are skewed, the cookie may expire
immediately after being sent to the client (browser). The default value of false sets
the cookie expiration time to ‘-1’, which means that the cookie persists until the client
window is closed. However, if the client sends a cookie that refers to a session that
has expired (and the current request does not refer to a session), the server ensures
that the cookie expires immediately.