The properties listed on this section are used to configure actions to trigger when certain events take place.

• wrapper.check.deadlock.action (3.5.0)

  Configures the actions to take place whenever deadlocks are detected.

• wrapper.filter.action.<n> (3.5.17)

  Configure the actions to take place whenever filters are triggered.

• wrapper.ping.timeout.action (1.0.0)

  Configures the actions to take place whenever the ping timeout has expired.

• wrapper.share.<n>.background.success.action (3.5.52)

  Configure the actions to take place whenever a share is successfully mapped in the background after startup.

• wrapper.share.<n>.background.failure.action (3.5.52)

  Configure the actions to take place whenever a share fails to be mapped with a permanent error after startup.

• wrapper.timer.<n>.action (3.3.0)

  Configure the actions to take place whenever timers are fired.

Possible actions for these properties are:

• DEBUG:

  will cause a debug message to be logged. This is only really useful in helping to understand when the action is fired.

• STATS (Since ver. 3.5.52, Standard/Professional Edition):

  will print performance statistics.

• DUMP:

  will invoke a thread dump.

• GC (Since ver. 3.5.7):

  will invoke a full garbage collection sweep in the JVM. Be aware that doing this frequently can affect performance of the JVM, as a full sweep will often cause all threads to freeze for the duration of the GC.

• RESTART:

  will stop the current JVM and then restart a new invocation.

• SHUTDOWN:

  will stop the JVM as well as the Wrapper.

• USER_<n> (Professional Edition):

  will cause a user-defined event to be fired. This can be either the sending of an email, or the execution of an external system command. The command could be anything from performing cleanup operations to raising an SNMP trap.

• PAUSE:

  will pause the Java application if pausing is enabled and the JVM is running. See the wrapper.pausable property for details.

• RESUME:

  will resume the Java application if it is in a paused state. This could be used if the JVM is not stopped when paused. See the wrapper.pausable property for details.

• SUSPEND_TIMEOUTS_<n> (Since ver. 3.5.40, Standard/Professional Edition):

  Tells the Wrapper to suspend all timeouts used when the JVM is not responding. <n> specifies the number of seconds to suspend timeouts, and should be in the range 1-3600 (1h). This could be used if the Java application needs to perform a long blocking task and avoid having the Wrapper considering the application as unresponsive.

  Timeouts can also be suspended via other action properties, the command file or the Java WrapperManager.suspendTimeouts() method.

  If several requests to suspend timeouts are made, the number of seconds specified by each request will not be summed. Instead, the newly specified time will replace the remaining suspension time if it is longer, and will be ignored otherwise.

• RESUME_TIMEOUTS (Since ver. 3.5.40, Standard/Professional Edition):

  Tells the Wrapper to resume all timeouts previously suspended.

  Timeouts can also be resumed via other action properties, the command file or the Java WrapperManager.resumeTimeouts() method.

• SUCCESS (Since ver. 3.5.5):

  will tell the Wrapper to reset its internal failed invocation count and count the current JVM invocation as "successful". This is probably not useful in this context, but is here for consistency with other properties.

• NONE:

  will tell the Wrapper to log the fact that a deadlock was detected, but it will not actually do anything.