Java 2 SDK for Solaris Developer's Guide

Java HotSpot VM Equivalents of Exact VM Options

For additional information on issues related to the Java HotSpot VM, see the online documentation at

Prior to version 1.3.0, the production releases of the Java 2 SDK for the Solaris Operating Environment shipped with a virtual-machine implementation known as the Exact VM (EVM). Beginning with version 1.3.0, the Exact VM is replaced by the Java HotSpot VM.

Some options supported by the Exact VM have changed names or become obsolete in the Java HotSpot VM. These EVM options and their Java HotSpot VM equivalents in Java 2 SDK v 1.4.0 are given in the following table.

EVM Option 


Java HotSpot VM equivalent 


Instruction tracing 

None (obsolete option) 


Method tracing 

None (obsolete option) 


Maximum java stack size 

None (Java HotSpot VM doesn't have separate native and Java programming language stacks) 


Verify heap integrity 





-XX:+VerifyAfterScavenge (all debug only)


Maximum compiled code size 

-Xmaxjitcodesize (used to be -Xmaxjitcodesize=32m, now -Xmaxjitcodesize32m)


Configure the heap 

(See The -Xgenconfig Option below.)


Use optimizing JIT Compiler 



Use concurrent garbage collector (1.2.2_07+) 

None (not yet in 1.3, 1.4) 

The Java HotSpot VM currently recognizes the following -X options that were not supported by the Exact VM.




Use Train GC 


Do not use Train Garbage Collection (default) 


Max percentage o fhead free after GC to avoid shrinking (default 0.7) 


Min percentage of heap free after GC to avoid expansion (default 0.4) 


Interpreter only 


Bind user-level threads (default in 1.4, not in 1.3) 


Set the size of the young generation (1.4 only)