Java Options Framework
The Java Options Framework contributes arbitrary Java options to the application at runtime.
|Detection Criterion||java_opts set in the config/java_opts.yml file or the JAVA_OPTS environment variable set|
Tags are printed to standard output by the buildpack detect script
For general information on configuring the buildpack, including how to specify configuration values through environment variables, refer to Configuration and Extension.
The framework can be configured by creating or modifying the
config/java_opts.yml file in the buildpack fork.
||Whether to append the value of the
||The Java options to use when running the application. All values are used without modification when invoking the JVM. The options are specified as a single YAML scalar in plain style or enclosed in single or double quotes.|
JAVA_OPTS from either the config file or environment variables that configure memory options will cause deployment to fail as they're not allowed. Memory options are configured by the buildpack and may not be modified.
JAVA_OPTS from either the config file or environment variables will be specified in the start command after any Java Opts added by other frameworks.
Java options will have special characters escaped when used in the shell command that starts the Java application but the
\ characters will not be escaped. This is to allow Java options to include environment variables when the application starts.
cf set-env my-application JAVA_OPTS '-Dexample.port=$PORT'
If an escaped
\ character is needed in the Java options they will have to be escaped manually. For example, to obtain this output in the start command.
From the command line use;
cf set-env my-application JAVA_OPTS '-Dexample.other=something.\\\\\$dollar.\\\\\\\slash'
config/java_opts.yml file use;
from_environment: true java_opts: '-Dexample.other=something.\\$dollar.\\\\slash'
Finally, from the applications manifest use;
env: JAVA_OPTS: '-Dexample.other=something.\\\\\$dollar.\\\\\\\slash'
# JAVA_OPTS configuration --- from_environment: false java_opts: -Xloggc:$PWD/beacon_gc.log -verbose:gc
JAVA_OPTS are restricted and will cause the application to fail deployment.
Allowed Memory Settings
Setting any of the allowed memory settings may require a change to the Memory Weightings. Where a value is shown it is the default value for that setting.
||Maximum size of young generation, known as the eden region. This could effect the total heap size Memory Weightings.|
||Use a policy that limits the proportion of the VM's time that is spent in GC before an
||Use large page memory. For details, see Java Support for Large Memory Pages.|
||Dump heap to file when
||Path to directory or filename for heap dump.|
||Sets the large page size used for the Java heap.|
||Upper limit on the maximum amount of allocatable direct buffer memory. This could effect the Memory Weightings.|
||Maximum percentage of heap free after GC to avoid shrinking.|
||Maximum size of new generation. Since
||Minimum percentage of heap free after GC to avoid expansion.|
||Ratio of old/new generation sizes. 2 is equal to approximately 66%.|
||Default size of new generation. This could effect the total heap size Memory Weightings.|
||Run user-defined commands on fatal error.|
||Run user-defined commands when an
||Java 8 Only Maximum code cache size. Also know as
||Ratio of eden/survivor space. Solaris only.|
||Desired ratio of survivor space used after scavenge.|
||Thread stack size. (0 means use default stack size).|