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

In this case, the iTP WebServer serves 105 requests (higher multiple of Numstatic nearest to
the count value). Here, the 106th request will display the following error message:
Maximum connections reached: The server reached its maximum configured capacity.
with HTTP response code:
200 OK
To customize the error message, create a new message ID error-maximum-connection. This
customized message is displayed if the Message configuration directive is used in the <iTP
WebServer Deployment Directory>/conf/httpd.config
file with the new message ID.
For more information on the MaxConnections configuration directive and creating customized
error messages using the Message configuration directive, see the iTP Secure WebServer System
Administrator's Guide.
NOTE: To use the MaxConnections configuration directive, your iTP WebServer must be
configured for the static environment only, that is, the values of Numstatic and MaxServers
of the httpd process must be equal.
Configuring NSJSP for MyFaces Applications
When a MyFaces application runs on a NonStop system, it runs as an instance of NSJSP. Therefore,
before configuring the NSJSP environment, it is important to determine the load each instance of
NSJSP is expected to handle. This section describes the following configuration aspects:
•
“Configuring SessionBasedLoadBalancing” (page 245)
•
“Configuring Connector Threads” (page 246)
•
“Configuring TS/MP Specific Parameters” (page 247)
•
“Configuring Java Runtime Arguments” (page 249)
•
“Determining the Maximum Capacity of NSJSP Instance” (page 250)
Configuring SessionBasedLoadBalancing
The NSJSP Container maintains sessions in the form of serialized Java objects. Each session object
is identified by a unique identifier called the session-ID. The session-ID is sent to the HTTP client
either as a cookie or in the form of URL-rewriting. The name of the cookie is JSESSIONID and
when the user application creates a session, NSJSP generates the cookie (JSESSIONID) as the
name and session-ID as the cookie value. The session objects can either be kept in the process
memory or persisted in a persistent store (for example, a database table). When it is kept in the
process, it is available only for the process that created the session object. On the other hand, if
it is kept in a persistent store, it is available for any process in the NSJSP environment. When the
SessionBasedLoadBalancing
feature is enabled, all requests related to a particular session
are routed to the process that has the session object in its memory.
To enable the SessionBasedLoadBalancing feature, you must configure the servlet.ssc
object by editing the <iTP WebServer Deployment Directory>/conf/servlet.config
file on OSS. The servlet.ssc object is configured under the Server directive. The
SessionBasedLoadBalancing
feature is governed by the -DSaveSessionOnCreation
and -DSessionBasedLoadBalancing arguments in the Arglist of the Server directive.
•
-DSaveSessionOnCreation
Enables or disables saving the sessions into a persistent store during their creation time.
Syntax:
-DSaveSessionOnCreation=[ true | false ]
NonStop Platform Configurations 245