Configuring nsjsp for spring applications, Configuring sessionbasedloadbalancing – HP Integrity NonStop H-Series User Manual
Page 70
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 a customized
error message 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 static environment only, that is, the values of
Numstatic
and
MaxServers
of
the
httpd
process must be equal.
Configuring NSJSP for Spring Applications
When a Spring 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
•
•
Configuring TS/MP Specific Parameters
•
Configuring Java Runtime Arguments
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 a cookie the
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 a session object
is kept in a process, it is available only for the process that created it. If it is kept in a persistent
store, it is available for any process under 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 modify the configurations of
the
servlet.ssc
object in 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 in a persistent store during their creation time.
Syntax:
-DSaveSessionOnCreation=[ true | false ]
70
Configuring Spring Applications on NonStop Systems