904  
 905 .fi
 906 .if n \{\
 907 .RE
 908 .\}
 909 The
 910 \fB\-Xmx\fR
 911 option is equivalent to
 912 \fB\-XX:MaxHeapSize\fR\&.
 913 .RE
 914 .PP
 915 \-Xnoclassgc
 916 .RS 4
 917 Disables garbage collection (GC) of classes\&. This can save some GC time, which shortens interruptions during the application run\&.
 918 .sp
 919 When you specify
 920 \fB\-Xnoclassgc\fR
 921 at startup, the class objects in the application will be left untouched during GC and will always be considered live\&. This can result in more memory being permanently occupied which, if not used carefully, will throw an out of memory exception\&.
 922 .RE
 923 .PP
 924 \-Xprof
 925 .RS 4
 926 Profiles the running program and sends profiling data to standard output\&. This option is provided as a utility that is useful in program development and is not intended to be used in production systems\&.
 927 .RE
 928 .PP
 929 \-Xrs
 930 .RS 4
 931 Reduces the use of operating system signals by the JVM\&.
 932 .sp
 933 Shutdown hooks enable orderly shutdown of a Java application by running user cleanup code (such as closing database connections) at shutdown, even if the JVM terminates abruptly\&.
 934 .sp
 935 The JVM catches signals to implement shutdown hooks for unexpected termination\&. The JVM uses
 936 \fBSIGHUP\fR,
 937 \fBSIGINT\fR, and
 938 \fBSIGTERM\fR
 939 to initiate the running of shutdown hooks\&.
 940 .sp
 941 The JVM uses a similar mechanism to implement the feature of dumping thread stacks for debugging purposes\&. The JVM uses
 942 \fBSIGQUIT\fR
 943 to perform thread dumps\&.
 944 .sp
 945 Applications embedding the JVM frequently need to trap signals such as
 946 \fBSIGINT\fR
 947 or
 948 \fBSIGTERM\fR, which can lead to interference with the JVM signal handlers\&. The

 904  
 905 .fi
 906 .if n \{\
 907 .RE
 908 .\}
 909 The
 910 \fB\-Xmx\fR
 911 option is equivalent to
 912 \fB\-XX:MaxHeapSize\fR\&.
 913 .RE
 914 .PP
 915 \-Xnoclassgc
 916 .RS 4
 917 Disables garbage collection (GC) of classes\&. This can save some GC time, which shortens interruptions during the application run\&.
 918 .sp
 919 When you specify
 920 \fB\-Xnoclassgc\fR
 921 at startup, the class objects in the application will be left untouched during GC and will always be considered live\&. This can result in more memory being permanently occupied which, if not used carefully, will throw an out of memory exception\&.
 922 .RE
 923 .PP





 924 \-Xrs
 925 .RS 4
 926 Reduces the use of operating system signals by the JVM\&.
 927 .sp
 928 Shutdown hooks enable orderly shutdown of a Java application by running user cleanup code (such as closing database connections) at shutdown, even if the JVM terminates abruptly\&.
 929 .sp
 930 The JVM catches signals to implement shutdown hooks for unexpected termination\&. The JVM uses
 931 \fBSIGHUP\fR,
 932 \fBSIGINT\fR, and
 933 \fBSIGTERM\fR
 934 to initiate the running of shutdown hooks\&.
 935 .sp
 936 The JVM uses a similar mechanism to implement the feature of dumping thread stacks for debugging purposes\&. The JVM uses
 937 \fBSIGQUIT\fR
 938 to perform thread dumps\&.
 939 .sp
 940 Applications embedding the JVM frequently need to trap signals such as
 941 \fBSIGINT\fR
 942 or
 943 \fBSIGTERM\fR, which can lead to interference with the JVM signal handlers\&. The