Red Hat NETSCAPE ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manual do Utilizador descarregar pdf (Página 50)

JSP Debugging

50 iPlanet Web Server, Enterprise Edition Programmer’s Guide to Servlets • May 2001

2. Set the following parameters in jvm12.conf as appropriate:

jvm.enableDebug=1

java.compiler=NONE

To send exceptions to the client in addition to the log file, set the following

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

example, for Solaris platforms, if Java 1.2 is in

/java, you set it as follows in

jvm12.conf:

jvm.option=-Xbootclasspath:/java/lib/tools.jar:/java/jre/lib/rt.jar

5. Start the server manually and record the password for remote debugging (this

is displayed on the console).

6. Start the Java debugger:

jdb -host your_host -password the_password

You should be able to debug your Java classes now using the jdb command.

JSP Debugging

You can debug your JSPs by following these steps:

1. Make sure that the server is running in single-process mode. Single-process

mode is the default, but you can check in the file

magnus.conf to make sure

that the

MaxProcs parameter is not set to a value greater than 1. If you do not

see a setting for

MaxProcs in magnus.conf, the default value of 1 is enabled for

it. For more information about single process mode versus multi-process

mode, see the iPlanet Web Server Administrator’s Guide.

2. Set the following parameters in jvm12.conf as appropriate:

java.compiler=NONE

jvm.trace=6

nes.jsp.enabledebug=1

1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 123 124

Sem comentários

Red Hat NETSCAPE ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manual do Utilizador Página 50