Using JVM Environment Variables
106 iPlanet Web Server, Enterprise Edition Programmer’s Guide to Servlets • May 2001
Here is an example jvm12.conf file. The jvm.classpath value must be all on one
line in the actual file.
[JVMConfig]
#jvm.minHeapSize=1048576
#jvm.maxHeapSize=16777216
#jvm.enableClassGC=0
#jvm.verboseMode=1
#jvm.enableDebug=1
#jvm.printErrors=0
#jvm.option=-Xrunoii
#jvm.profiler=optimizeit
#jvm.disableThreadRecycling=0
#jvm.serializeAttach=0
#jvm.stickyAttach=0
#jvm.trace=5
#java.compiler=NONE
#OPTITDIR=D:/App/IntuitiveSystems/OptimizeIt30D
#jvm.serializeFirstRequest=0
#jvm.include.CLASSPATH=1
#nes.jsp.forkjavac=0
#nes.jsp.enabledebug=1
jvm.classpath=/usr/java/tools.jar
Generally you should use plain property options (like name=value) for the JDK1.2
configuration and
jvm.option=options for JVM-vendor dependent configurations.
There can be multiple occurrences of
jvm.option parameters.
A list of debugging options that you can include in the
jvm12.conf file if the JPDA
is installed is available here:
http://java.sun.com/products/jpda/doc/conninv.html#Invocation
For more information about debugging servlets and JSPs and the jvm12.conf
parameters required for debugging, see Chapter 5, “Debugging Servlets and JSPs.”
Using JVM Environment Variables
If you define JVM environment variables using the jvm.option setting in the
jvm12.conf file or the Administration Server, servlets do not recognize them. Just
use the plain name
=value format for environment variables.
When you are running a stand-alone command line java program, use the
following option to pass system properties into the java program:
java -Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB myprogram
Commenti su questo manuale