[Wrapper-user] Automatic adaption of detailed JVM parameters like -Xmn to system memory

[Isenberg, H. <ise...@e-...>]

With wrapper.java.maxmemory.percent a fraction of the system memory can be automatically assigned to the JVM to be used as overall heap limit. That is working fine, but for our server software, more specific JVM parameters are required as wrapper.java.additional like -Xmn or -XX:MaxMetaspaceSize or -XX:ReservedCodeCacheSize. For now, the values for these parameters are set to absolute numbers by our post-install script.

For automatic app deployment, a setting as fraction like maxmemory.percent is preferable so the process would automatically resize on the next start after the machine memory is increased.

Is someone using a workaround with using wrapper.java.additional_file to set environment variables to be read afterwards or something else to achieve setting percent values in wrapper.java.additional?

--
Holger Isenberg
e-Spirit AG