NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator's Guide
Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 7.0 System Administrator’s Guide—674372-005
3-31
The Installation-Specific servlet.config File
It is necessary that HTTP GET request contains one of two new request
parameters Serverclass or Process. As mentioned above these parameters
are provided to determine the scope of the JMX operation. If both the
parameters are provided the operation will be executed on the specified
process in the specified server class. If none of them are provided, an error will
be returned.
The error messages, if any, displayed may look slightly different from NSJSP
6.1 JMX Proxy error messages. The results may also contain the list of the
processes for which the error(s) happened.
As expected, the JMX Servlet will now be invoked using the NSJSP Manager's
base URL. For example,
http://<NSJSP Host:Port>/manager/jmxproxy/…
SaveSessionOnCreation
Enables or disables saving sessions into a persistent store during creation time.
The default value is false. This is to prevent saving a session before it is modified
by the user application. This also reduces the number of database operations for
each client request.
If both the SaveSessionOnCreation and the SessionBasedLoadBalancing
options are set to false, and if a persistent manager is configured with a
persistent store, then 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.
Note.
NSJSP 6.1 JMX Proxy did not provide an option to run a JMX operation on a
specific NSJSP Process.
JMX Proxy URL workls only of / is provided before ? in the URL name. The
following is an example of a correct URL:
http://15.146.232.231/manager/jmxproxy/?serverclass=SERVLETS
. Tomcat also exhibits the same behaviour.
Caution. Running a "list" or a "get" JMX operation on an individual process can be
quite helpful for troubleshooting NSJSP problems, but one should avoid using "set"
JMX operations on the individual NSJSP processes. Running "set" JMX operation on
individual process will cause processes to be out of synch with each other. It will also
result in the inconsistency on the data being displayed in NSJSP Manager.