DO 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.
Most users should not need to modify this property.
Number of seconds to allow asynchronous startup operations to complete before
the Wrapper continues with the startup process. Normally this should be set long
enough for the operations to complete before continuing, but this timeout
prevents very slow startups on some systems. On most systems these startup
operations complete within 100 milliseconds.
Valid values are in the range of "1" to "3600" seconds, where "0" (zero) will not wait at all.
The default value is "2 seconds".
Starting with Wrapper version 3.5.7, the Wrapper binaries on Windows are signed to
prevent tampering and certify the origin of the binaries.
In addition to the checks performed by the OS, the Wrapper also calls
to collect and report information about the certificate chain of the binary.
The Wrapper also uses this information to shutdown the Wrapper if a corrupted binary is detected.
On most systems, the WinVerifyTrust call completes within a fraction of a
second. On some systems however, Windows can take a long time to complete
this operation. The delays appear to be related to attempts to access
updated versions of the CRL file from Microsoft's server.
The default timeout of 2 seconds is short enough that the Wrapper startup
will feel responsive, but long enough to allow the startup to complete in
the majority of cases. If the timeout expires, the startup operations will
continue in the background. Usually this will only result in the certificate
chain being reported late in the log files, but it could also result in the
Wrapper deciding to shutdown after the JVM has been launched if a corrupted
binary is detected. For these reasons, it is not recommended that the
timeout be set shorter than the default 2 seconds.