Technical references : Administration : Tanuki service wrapper configuration : Planon configuration : Generic configuration changes
Generic configuration changes
• On top of the configuration file some parameters are defined by default. They are referenced in the file with the following concept %parameter name%. You can use this concept for own parameters too. The parameters are formatted as follows. For example application server Java home: set.JAVA_HOME=[JAVA_HOME]. For all parameters see the configuration files.
• On startup of the service details about environment and JVM are logged:
wrapper.environment.dump=TRUE
wrapper.java.version.output=TRUE
• Ignore gaps in numbering in wrapper.java.additional parameters:
wrapper.ignore_sequence_gaps=TRUE
• The option wrapper.ping.timeout already existed and it is set to 1800 seconds (half an hour). Previously, the service would try to restart the JVM after that time. Now, this behavior is extended to also log a thread-dump:
wrapper.ping.timeout.action=DUMP,RESTART
• Log a warning if the JVM does not respond within this period (number of seconds).
wrapper.ping.alert.threshold=10
• The following parameters can be used to limit the size of the log file and to set a maximum size so that the file size does not grow unmanageably:
wrapper.logfile.maxsize=10m
wrapper.logfile.maxfiles=10
The log file size may be abbreviated as 'k' (kb) or 'm' (mb) as the suffix for the integer. For example, 10m = 10 megabytes.
* 
The default value is set to 10m and 10 files.
Setting the maximum size to the log file is not mandatory.
* 
To allow the log file to expand unrestrictedly, remove the previous two lines from the jboss-wrapper-default.conf file, but be aware that this can cause disk space issues in future.