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:

• wrapper.wait_for_hostid property
• wrapper.wait_for_hostid.strict property
• wrapper.wait_for_hostid.timeout property
• wrapper.max_hostid_timeout property (Deprecated)

wrapper.wait_for_hostid

Compatibility : 3.4.0 Editions : Platforms : Tells the Wrapper to wait for Network Interfaces at startup. When starting as Daemon, The default value is "TRUE", "FALSE" otherwise. Example: wrapper.wait_for_hostid=TRUE 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.

wrapper.wait_for_hostid.strict

Compatibility : 3.5.41 Editions : Platforms : This property can be set to TRUE to force waiting for a specific HostId up to the value of wrapper.wait_for_hostid.timeout. The default value is "FALSE", which tells the Wrapper to stop waiting once at least one network interface is found. NOTE Before version 3.5.41, the Wrapper always waited for the license's HostId to be available, hence behaved the same as when wrapper.wait_for_hostid.strict is set to TRUE.

wrapper.wait_for_hostid.timeout

Compatibility : 3.5.41 Editions : Platforms : Configures the maximum number of seconds that the Wrapper will wait for the Network Interfaces to come up. Up to this time, the Wrapper will check for the interfaces once every second. The default value is "15" seconds. Example: (30 seconds) wrapper.wait_for_hostid.timeout=30

wrapper.max_hostid_timeout

Compatibility : 3.4.0 (Deprecated as of 3.5.41) Editions : Platforms : WARNING Use of this property has been deprecated as of Wrapper version 3.5.41 in favor of the wrapper.wait_for_hostid.timeout property.

• wrapper.cpu.timeout (2.2.8)

  Configures the number of seconds without CPU before the JVM sends a warning and extend timeouts.

• wrapper.max_hostid_timeout (3.4.0) ( Std/Pro )

• wrapper.logfile.close.timeout (3.5.21)

  Controls the number of seconds at which the log file should close after the last log entry.

• wrapper.logfile.flush.timeout (3.5.21)

  Configures the interval in seconds at which the Wrapper flushes all outputs to the log file.

• wrapper.logfile.inactivity.timeout (3.2.0, deprecated as of 3.5.21)

  Controls the number of seconds at which the log file should close after the last log entry.

• wrapper.ping.timeout (1.0.0)

  Configures the number of seconds to allow between two ping responses coming from the JVM.

• wrapper.startup_thread.timeout (3.5.11)

  Configures the number of seconds to allow asynchronous startup operations to be completed.

• wrapper.startup.timeout (1.0.0)

  Configures the number of seconds to allow between the time the Wrapper launches the JVM and the time the JVM responds that the application has started.

• wrapper.shutdown.timeout (2.2.7)

  Configures the number of seconds to allow between the time the Wrapper asks the JVM to shutdown and the time the JVM responds that it is stopping.

• wrapper.jvm_exit.timeout (2.2.8)

  Configures the number of seconds to allow between the time the JVM reports it is stopped and the time the JVM process actually terminates.

• wrapper.jvm_cleanup.timeout (3.4.0)

  Configures the number of seconds allowed for the Wrapper to clean up child processes after the JVM has been shutdown.

• wrapper.jvm_terminate.timeout (3.5.18)

  Configures the number of seconds to allow from the time that the Wrapper asks the system to forcibly terminate the JVM until it confirms that the process actually stopped.

• wrapper.event.<event_name>.command.block.timeout (3.3.0) ( Pro )

  Configures how long the Wrapper will wait for a configured event to complete.

• wrapper.event.<event_name>.email.receive.timeout (3.3.2) ( Pro )
• wrapper.event.<event_name>.email.send.timeout (3.3.2) ( Pro )