wrapper.logfile.close.timeout
Compatibility :3.5.21
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSXLinuxIBM AIXFreeBSDHP-UXSolarisIBM z/Linux

When the JVM application is idle for long periods of time, the Wrapper by default will close its log file so it can be deleted or manipulated in other ways. This property controls the number of seconds since the last log entry after which the log file will be closed.

Possible values are in the range of "0" to "3600" seconds, or "-1" to completely disable closing the file. A value of "0" (zero) will cause the log file to be closed immediately after each log entry is written to disk.

The default value is "1" second.

Example:(1 second) 
wrapper.logfile.close.timeout=1

NOTE

wrapper.logfile.close.timeout is ignored for Wrapper invocations used to control the Wrapper as a service (wrapperm). For these invocations, the log file is always closed after each entry is written to disk so as not to block the log file which must remain accessible to the running service instance.

When the log file is closed, any unflushed log output will be flushed automatically. The interval at which the log file is flushed can be controlled using the wrapper.logfile.flush.timeout property.

WARNING

The value of "0" (zero) will have a noticeable performance impact on the Wrapper, as it will become necessary to open and close the file for every single line of output.

NOTE

For backwards compatibility, this property gets its default value from the deprecated wrapper.logfile.inactivity.timeout property (which existed since Wrapper version 3.2.0, and deprecated as of Wrapper version 3.5.21).

Reference: logfile