HP Integrity NonStop H-Series - Manual (Page 314)

NOTE: When the SessionBasedLoadBalancing feature is turned ON, messages
are delivered to NSJSP not only through TS/MP but also through file system calls. Hence,
there could be a situation that all the messages delivered to a particular dynamic process
are through file system calls and none through TS/MP. Therefore, TS/MP may assume
that a particular dynamic process is not required any more and will shut down the
process. However, that dynamic process can have valid session objects in memory,
which will be lost if the process is shutdown. With the
SessionBasedLoadBalancing
feature turned ON, it is important not to configure the dynamic processes.
Enabling or disabling the SessionBasedLoadBalancing feature depends on the
application requirement. Your Hibernate 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 (such as 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.0 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
• Configuring the Executor Element
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:
…
…
<Service name=”NSJSP”>
<Connector protocol="HTTP/1.1"
connectionTimeout="0"
314 Configuring Hibernate Applications on NonStop Systems