Compatibility :	3.5.5
Editions :
Platforms :

Setting this property to TRUE will cause the Wrapper to go immediately into a paused state, without ever launching a JVM.

This can be very useful for failover systems which should only be launched under the correct circumstances. Being in a paused state lets the Wrapper monitor its commandfile or other input for a trigger to start up the JVM and its application.

This property will be ignored unless the wrapper.pausable property is also set to TRUE.

The default value is "FALSE".

wrapper.pause_on_startup=FALSE

• wrapper.ntservice.pausable (3.2.1, deprecated as of 3.5.0)

  Allows to pause and resume the service from the Services panel or from the command line.

• wrapper.ntservice.pausable.stop_jvm (3.2.1, deprecated as of 3.5.0)

• wrapper.pausable (3.5.0)

  Enables the PAUSE and RESUME actions.

• wrapper.pausable.stop_jvm (3.5.0)

  Specifies if the JVM should be stopped when the Wrapper is paused, or if the Java application should handle a control event to pause itself.

• wrapper.pause_on_startup (3.5.5)

  Causes the Wrapper to go immediately into a paused state, without launching a JVM.