• wrapper.daemonize property
• wrapper.wait_for_hostid property
• wrapper.max_hostid_timeout property

Compatibility :	3.0.0
Editions :
Platforms :

This property is only used on Linux/UNIX platforms.

Spawns a fork of the Wrapper process as a detached non-session group leader. This means that the process will continue to run even after the console from which the Wrapper process was launched has been closed.

In most cases, this property will not be set from within the wrapper.conf file. It can be passed to the Wrapper process by the shell script which launches the Wrapper. An example can be found in the sh.script.in file in the src/bin directory.

wrapper.daemonize=TRUE

Compatibility :	3.4.0
Editions :
Platforms :

This property is only used on Linux/UNIX platforms.

Enables the Wrapper to wait for the host Id at startup.

With the release of 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. In order to defuse this race-condition, please use this property.

When starting as Daemon, The default value is "TRUE", "FALSE" otherwise.

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.

wrapper  | Waiting for hostId(s)... (System HostId(s): xxxxx

It has already been seen that some network interfaces however won't be up due to some Network Manager who set up the interface (especially WiFi interfaces) for instance by default at log in. It is therefore recommended to use the Ethernet interface when it's desired to start the Wrapper during booting a machine.

Compatibility :	3.4.0
Editions :
Platforms :

This property is only used on Linux/UNIX platforms.

Sets the timeout how many seconds the Wrapper will at max wait for the Network Interfaces to come up.

The property takes as argument the maximum amount of seconds the Wrapper should wait for the interfaces to get up. Up to this time, the Wrapper will check for the interfaces once every second. The default value is "0" (zero) second, which means never time out and the Wrapper will indefinitely loop until a valid interface has been detected.

wrapper.max_hostid_timeout=30

• 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 )

  Configures the maximum number of seconds the Wrapper should wait for network interfaces to come up.

• 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 )