| Compatibility : | 3.3.0 |
| Editions : |    |
| Platforms : |          |
This property specifies what wrapper will do after the command exited, depending on its exit code.
Like several of the event command properties, it can be defined:
-
Globally for all events: wrapper.event.default.command.on_exit.<n> property, or
-
For a specific event: wrapper.event.<event_name>.command.on_exit.<n> property.
The "<event_name>" component of the property name can be
either the keyword "default",
or one of the Event Types.
By setting the default property,
all Event Types which are not set explicitly will take on that value.
The "<n>" component of the property name is an exit code.
The wrapper.ignore_sequence_gaps
property can optionally be set to allow gaps in the sequence.
This is helpful for instance if any preparation routine, started as command by the Wrapper signaled,
that it didn't exit with code 0 and therefore you don't want your main application to get started.
| Example: |
wrapper.event.jvm_prelaunch.command.argv.1=/usr/bin/mypreparation
wrapper.event.jvm_prelaunch.command.argv.2=parameter1
wrapper.event.jvm_prelaunch.command.block=TRUE
wrapper.event.jvm_prelaunch.command.block.timeout=30
wrapper.event.jvm_prelaunch.command.onexit.default=SHUTDOWN
wrapper.event.jvm_prelaunch.command.onexit.0=IGNORE
|
By default, the Wrapper will ignore any exit codes and continue running.
|
