Default Java heap sizes when -Xms and -Xmx are not specified

(Doc ID 1042595.1)

Last updated on JULY 12, 2018

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 5.1.0 to 6.1.5 [Release 5.x to 6.x]
Information in this document applies to any platform.

Goal

Default Java heap sizes when -Xms and -Xmx are not specified.

Endeca provides options to use the Java -Xms and -Xmx flags to override the initial and maximum Java heap sizes for JVMs started by Forge (via the --javaArgument flag), the Report Generator (via <java-option> elements in the Deployment Template's AppConfig.xml file), and similar Java-based or Java-using components. 

What are the default initial and maximum Java heap sizes if the -Xms and -Xmx Java flags are not specified? 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms