Index |
|
wrapper.java.additional.<n> |
||||||||||
Additional Java parameters to pass to Java when it is launched. These are not parameters for your application, but rather parameters for the JVM. <n> component:
Each element has a property name which starts with "wrapper.
It is important that each property only define a single argument to the JVM. If the value needs to include a space, then it is necessary to add quotes following the rules described below.
NOTE
For application specific properties, especially those with values containing sensitive data, consider using wrapper. NOTE
When the wrapper. If you wish to dynamically change the list of additional Java parameters, there are a few ways to do so. The first is to make use of cascading include files to append a generated configuration file listing the wrapper.java.additional.<n> properties along with your JVM options. Alternatively, you may use the wrapper.java.additional_file property to reference a parameter file where you would simply list the JVM options without properties. Finally, you can pass the wrapper.java.additional.<n> as command line properties when launching the Wrapper. |
wrapper.java.additional.<n>.stripquotes |
||||||||||
If a wrapper.
The wrapper.
Defaults to the value of the wrapper. <n> component:
Each element has a property name which starts with "wrapper.
The following replacements will be made when stripping quotes. All other characters will remain unchanged.
|
wrapper.java.additional.<n>.java_version.min |
||||||||||
This property can be used to append the option with index 'n' only if the Java version is greater than or equal to the specified value. The default value is '1.4' which is the oldest JVM version supported by the Wrapper. Any lower value is invalid and will cause the Wrapper to stop. The value can be in the format '1.major[.minor[_revision]]' or 'major[.minor[.revision]]', regardless the version of Java. This is done to support both numbering schemes returned by 'java -version': prior to Java 9 the first format was used, while Java 9 and above use the second format. The brackets indicate that the minor and revision components are optional. Leaving one or both unspecified means that these placeholders will accept any number.
WARNING
|
wrapper.java.additional.<n>.java_version.max |
||||||||||
This property can be used to append the option with index 'n' only if the Java version is lower than or equal to the specified value. The default value is 'UNLIMITED'. The value can be in the format '1.major[.minor[_revision]]' or 'major[.minor[.revision]]', regardless the version of Java. This is done to support both numbering schemes returned by 'java -version': prior to Java 9 the first format was used, while Java 9 and above use the second format. The brackets indicate that the minor and revision components are optional. Leaving one or both unspecified means that these placeholders will accept any number.
WARNING
|
wrapper.java.additional.<n>.app_only |
|||||||||
WARNING
Use of this property has been deprecated as of Wrapper version 3.5.60 in favor of the
wrapper. Before launching a JVM to run the Java application, the Wrapper will execute the Java command line with a --dry-run option to check that the command line is valid.
The wrapper. This property has no effect when using versions of Java that do not support the --dry-run option (prior to Java9). The default value is "FALSE", which means that the specified option will be present in both the real Java command line and the "--dry-run" command line. In the vast majority of cases, FALSE is preferred so that all JVM options are checked. NOTESetting this property to TRUE will bypass the validity check for the specified option.
There are a few cases where setting wrapper.
Most of the time, this warning won't be visible because the output will be logged at the level specified with the wrapper.java.query.loglevel property, which is DEBUG by default. However, it is not possible to track the native memory usage of a "--dry-run" JVM anyway because it won't run user's native code. It is therefore best not to include this option in the "--dry-run" command line.
|
wrapper.java.additional.<n>.scope |
|||||||||
WARNINGDO NOT modify any of these parameters unless you have read this property description. Incorrect settings can cause the Wrapper to fail to operate as expected. Before launching the Java application, the Wrapper will run the java command a few times to determine the characteristics of the current Java installation and the appropriate settings for the application. In most cases, the command lines for these Java invocations are built by the Wrapper without the user having to worry about it. In a few rare scenarios, however, it may be necessary to add or remove certain options to these command lines. Let's first draw the list of these Java invocations and their roles:
The wrapper. Possible values are:
The default value is DRYRUN_APP.
|
wrapper.java.additional_file |
||||||||
In certain cases, it can be inconvenient to list up your Java parameters in the Wrapper configuration file. This property provides a way to specify a file which can contain one or more parameters that will be passed as is to the JVM when it is launched. This can be very useful when the parameter list needs to be generated dynamically or via an installer. Any parameters defined in this file will appear after those defined using the standard wrapper.java.additional.<n> properties. Starting with Wrapper version 3.5.23, any environment variable references in the file will be expanded. NOTEYou may target different versions of Java by including the WRAPPER_JAVA_VERSION environment variable in the name of the file. Parameter File Format: The file format is simple.
|
wrapper.java.additional_file.required |
||||||||
Specifies if the Java additional file is required or not. If it is required and not found, the Wrapper will stop without starting the JVM. If it is not required, the file will be ignored when not found. The default value is TRUE.
|
wrapper.java.additional_file.stripquotes |
||||||||||
Different platforms handle parameters with spaces differently. To make a given configuration work consistently, you should always quote those values. They will be used as is on Windows. However, on UNIX platforms, the quotes will be stripped as the command line is broken into a parameter list. In almost all cases you will want to strip these quotes. The default value is "FALSE".
|
Usage Examples |
||||||
|
Reference: Parameters |
|