HP Integrity NonStop J-Series - Manual (Page 326)

NOTE: The default value is true.
While setting these arguments, consider the following:
1.
If both theSaveSessionOnCreation and SessionBasedLoadBalancing options
are set to false, and if a Persistent Manager is configured with a persistent store, 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.
2. Enabling or disabling the SessionBasedLoadBalancing feature depends on the
application requirement. Your application might encounter any of the following scenarios:
◦ The application depends heavily on the state stored in session objects. Therefore,
session objects cannot be lost and the application cannot recover from loss of state.
◦ Application response is of prime importance and the application can recover from
a loss of state.
◦ The application is expected to handle largely varying loads and having a large
number of static NSJSP instances is not an option.
◦ The session objects must be valid for large durations (like an entire day).
◦ The session objects must be available whenever the application restarts.
For more information on the SessionBasedLoadBalancing and
SessionBasedLoadBalancing
configuration directives, see the NonStop Servlets for
JavaServer Pages (NSJSP) 6.1 System Administrator's Guide.
Configuring Connector Threads
The Connector is responsible for creating and maintaining the threads that are used for message
processing. A thread is allocated for each incoming message; therefore, the number of messages
that can be processed simultaneously can be controlled by limiting the number of threads that
NSJSP Connector can spawn.
NOTE: A single connector can service multiple instances of the container. The connector must
be configured such that it can spawn threads sufficient for all the container instances. In terms of
configuration, the Host element in the server.xml configuration file represents a container that
is serviced by the connector.
The NSJSP Connector thread pool can be connected using the following ways:
•
“Configuring the Connector Element” (page 326)
•
“Configuring the Executor Element” (page 327)
Configuring the Connector Element
Configure the maxThreads attribute of the Connector element in the <NSJSP Deployment
Directory>/conf/server.xml
file on OSS. The Connector element is the child element of
the Service element.
For example:
The following snippet shows the configuration in the <NSJSP Deployment
Directory>/conf/server.xml
file on OSS, if you want to configure 75 simultaneous connector
threads:
…
…
<Connector protocol="HTTP/1.1"
connectionTimeout="0"
acceptCount="25"
maxThreads="75"/>
…
326 NonStop Specific Configurations