To set this higher you need to modify /etc/system by adding the following 2 definitions: a try.
This uses the incremental garbage collection algorithm, which attempts to collect a fraction of the heap instead of the entire thing at once.
See Java SE Supported System Configurations for details. If you are having problems with the pause times for garbage collection or it taking too long, then see the pause time question above. What determines when softly referenced objects are flushed?
For more information, see the evaluation section of bug 4697804. The maximum theoretical heap limit for the 32-bit JVM is 4G.
For more in-depth troubleshooting discussion beyond the scope of this FAQ, please see the Java Trouble-Shooting and Diagnostic Guide I can't get profiling to work, what should I do?
First, make sure you are running with -agentlib:hprof and try -agentlib:hprof=help to see the different kinds of profiling available.
If you are still having problems please see the Java Trouble-Shooting and Diagnostic Guide I keep running out of file descriptors, what should I do?
Certain applications will use a lot of file descriptors.
On 32-bit Solaris kernels the address space is limited to 2G.