Health Check Alert: JVM Minimum and Maximum Heap settings need to be equal
(Doc ID 874792.1)
Last updated on JUNE 11, 2019
Applies to:Oracle WebLogic Server
Information in this document applies to any platform.
Information in this document applies to Any Linux,Any Unix,Any Solaris,Any Microsoft Windows,.
Health Check Category:
This document provides a quick reference explaining the following Health Check Alert:
My Oracle Support provides a proactive health check that automatically detects and notifies you of the existence of this issue before it impacts your business. To leverage this proactive support capability, install the Oracle Configuration Manager (OCM). Information on installing the Oracle Configuration Manager can be found on the Collector tab of My Oracle Support. To view the full portfolio of health checks available, see Note 868955.1
Checks if the JVM Minimum and Maximum Heap settings are not equal.
If the JVM heap is configured to allow growth and Oracle WebLogic Server is under heavy load, the CPU overhead of requesting additional memory to expand the JVM heap reduces the available CPU cycles for processing requests.
Assess the heap capacity necessary for the application and specify equal and fixed start and maximum heap size. Use the JVM parameters "-Xms" and "-Xmx" to specify these values. This best practice may improve the performance of the system under heavy load.
Please see the JVM tuning documentation for details.
Tuning the JRockit JVM
WebLogic Server Performance and Tuning