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

NOTE: The default value of -DSaveSessionOnCreation is false.
•
-DSessionBasedLoadBalancing
Enables or disables session-based load balancing.
Syntax:
-DSessionBasedLoadBalancing=[ true | false ]
NOTE: The default value of -DSessionBasedLoadBalancing is set to true.
For example, if you want to enable the SessionBasedLoadBalancing feature for your
Axis2/Java application and save the application sessions in a persistent store, set the Arglist
as:
Server $server_objectcode {
…
…
…
…
Arglist -DSessionBasedLoadBalancing=true \
-DSaveSessionOnCreation=true \
…
…
…
…
}
where,
server_objectcode is mapped to the servlet.ssc object in the <iTP WebServer
Deployment Directory>/bin directory on OSS.
While setting these arguments, consider the following:
1.
If both the SaveSessionOnCreation 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 Axis2/Java 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.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
NonStop Platform Configurations 313