NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator’s Guide—544548-004
3-20
Troubleshooting the Security Manager
By default, the NSJSP container runs without a Security Manager. You can set this
option to none if you do not want to use Security Manager. For example:
-Dnsjsp.security.manager=none
Troubleshooting the Security Manager
You can begin the Java Security Manager debug logging by including
java.security.debug=all in the file servlet.config before starting NSJSP.
The debug output is written to NSJSP_HOME/logs/servlet.out or
NSJSP_HOME/logs/servlet.err. You can specify more options in the
java.security.debug property. For information on Java Debugging Support, see
the online documentation located at
http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/debugger.html
.
Example 3-7 shows how to troubleshoot the Security Manager.
Example 3-6. Starting NSJSP with a Security Manager
#
# NSJSP Java2 System policy file and Java2 VM option.
#
# Note: the "double" equalto signs "==" is not a typo!! This informs
the JVM
# to use this file exclusively and that all others are to be ignored.
#
set env(JVM_POLICY_FILE) $env(NSJSP_HOME)/conf/iTP_catalina.policy
set NSJSP_SECMGR_POLICY -Djava.security.policy==$env(JVM_POLICY_FILE)
...
set NSJSP_SECMGR -Djava.security.manager
...
#
# This is the actual Arglist used to startup the NSJSP Container.
#
Arglist -Xmx64m -Xss128k -Xnoclassgc \
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \
-Djava.util.logging.config.file=$env(NSJSP_HOME)/conf/logging.properties
\
-Djavax.management.builder.initial=com.tandem.servlet.jmx.NSJSPMBean
ServerBuilder \
$NSJSP_SECMGR \
$NSJSP_SECMGR_POLICY \
$NSJSP_JAAS_CONFIG \
-Dcatalina.home=$env(NSJSP_HOME) \
-Dcatalina.base=$env(NSJSP_HOME) \
-Djava.io.tmpdir=$env(NSJSP_HOME)/temp \
org.apache.catalina.startup.Bootstrap start