wrapper.filter.<x>.<n> Properties

Search This Site:

Hosted by:
SourceForge

wrapper.filter.<x>.<n> Properties
Configuration Property Overview
wrapper.filter.trigger.<n> and wrapper.filter.action.<n>

The wrapper.filter pair of properties make it possible to filter the output of a JVM and then perform some action whenever a specific trigger string is found. The filtering process works by scanning through the triggers until a match is found. At that point the associated action is executed. Only the first matching trigger will be handled for any line of output. Each trigger/action pair ends with an integer number counting up from 1. There can be no missing numbers. If an action is omitted, it will default to RESTART.

The trigger can be any string. Possible actions are RESTART, SHUTDOWN, and NONE. RESTART will stop the current JVM and then restart a new invocation. SHUTDOWN will stop the JVM as well as the Wrapper. NONE is useful because it will prevent any triggers with a higher number from being triggered.

The following example will monitor the JVM output and then restart the JVM automatically whenever a java.lang.OutOfMemoryError is thrown to the console. Depending on where in an application the error is thrown, it is not always possible to trap and handle the error in a useful way from within the JVM.

Example:
wrapper.filter.trigger.1=java.lang.OutOfMemoryError
wrapper.filter.action.1=RESTART

The next example demonstrates how to trigger a JVM restart whenever the string Error appears anywhere in the output, with the exception of the case where the string is part of the larger string IgnoreError.

Example:
wrapper.filter.trigger.1=IgnoreError
wrapper.filter.action.1=NONE
wrapper.filter.trigger.2=Error
wrapper.filter.action.2=RESTART

by Leif Mortenson

last modified: