Jsp Debugging - Netscape ENTERPRISE SERVER 6.1 - PROGRAMMER GUIDE TO SERVLETS Programmer's Manual

JSP Debugging

Set the following parameters in
2.
jvm.enableDebug=1
java.compiler=NONE
To send exceptions to the client in addition to the log file, set the following
3.
parameter. If the client is a browser, exceptions are displayed in the browser.
jvm.trace=7
On some platforms, you may be required to specify the bootclasspath. For
4.
example, for Solaris platforms, if Java 1.4 is in
jvm12.conf
jvm.option=-Xbootclasspath:/java/lib/tools.jar:/java/jre/lib/rt.
jar
Start the server manually and record the password for remote debugging (this
5.
is displayed on the console).
Start the Java debugger:
6.
jdb -host your_host -password the_password
You should be able to debug your Java classes now using the
JSP Debugging
You can debug your JSPs by following these steps:
Make sure that the server is running in single-process mode. Single-process
1.
mode is the default, but you can check in the file
that the
see a setting for
it. For more information about single process mode versus multi-process
mode, see the Netscape Enterprise Server Administrator's Guide.
Set the following parameters in
2.
java.compiler=NONE
jvm.trace=6
nes.jsp.enabledebug=1
52 Netscape Enterprise Server Programmer's Guide to Servlets • April 2002 (Draft)
:
parameter is not set to a value greater than 1. If you do not
MaxProcs
in
MaxProcs magnus.conf
as appropriate:
jvm12.conf
, you set it as follows in
/java
magnus.conf
, the default value of 1 is enabled for
as appropriate:
jvm12.conf
command.
jdb
to make sure