This set of properties is only necessary for Wrapper instances using a Server License on Linux/UNIX platforms.
Development and Community Licenses will not require them.
Starting with Wrapper version 3.4.0,
it's possible to install/integrate the Wrapper into the boot scripts of UNIX platforms.
However, as the Server License is tied the hostId of a Network Interface,
it may happen that the interface is not yet available at an early time while the OS is starting up.
When installed as UNIX daemon, the Wrapper will defuse this race-condition by waiting for network interfaces to be available before validating a Server License.
By default the Wrapper waits (within the specified timeout) until at least one network interface is found,
but this behavior can be changed to keep waiting until the license's hostId is found.
The following set of properties makes it possible to enable/disable and configure this feature:
Tells the Wrapper to wait for Network Interfaces at startup.
When starting as Daemon, The default value is "TRUE", "FALSE" otherwise.
While waiting for an interface, the Wrapper will print out every 10 seconds a short notifier to
the log file that it is waiting for an interface.
Example of Log file:
wrapper | Waiting for hostId(s)... (System HostId(s): xxxxx
It has already been seen that some network interfaces (especially WiFi interfaces)
are configured to be up after the user logs in or at a stage happening after daemons
are started, hence can't be used by the Wrapper on startup.
It is, therefore, recommended to use the Ethernet interface
when it's desired to start the Wrapper during booting a machine.
Konfiguriert die Anzahl der Sekunden, die vergehen darf zwischen dem Zeitpunkt an dem der Wrapper ein erzwungenes Beenden der JVM beim System anfragt, bis zu dem Zeitpunkt an dem er bestätigt, dass der Prozess tatsächlich beendet wurde.