Compatibility :	3.1.2
Editions :
Platforms :

This property makes it possible to control to allow a given application to have a single invocation (TRUE) or multiple invocations at the same time (FALSE). The default value is to allow multiple invocations. The default value is "FALSE".

If single invocation is enabled (TRUE), then the Wrapper will look for a named "Mutex" in memory build by concatenating "Java Service Wrapper - " and the value of the wrapper.ntservice.name property. This means that it is possible to run multiple applications controlled by the Wrapper, while at the same time making sure that an individual application is not launched more than once.

This property can be useful in making sure that an application is not launched as a console application when running as a Windows Service; or vice versa.

wrapper.single_invocation=FALSE

• wrapper.single_invocation (3.1.2)

  Ensures that only one instance of the Wrapper is running at a given time.

• wrapper.single_invocation.notify (3.5.28) ( Std/Pro )

  Triggers an event and attempts to set focus to the running Java application when a second instance is launched.

• wrapper.single_invocation.notify.focus_window (3.5.28) ( Std/Pro )

  Sets the focus to the top window of the Java application whenever a second instance is launched.

• wrapper.single_invocation.notify.timeout (3.5.28) ( Std/Pro )

  Configures the maximum number of seconds that the Wrapper will wait for a reply from the running instance.

• wrapper.single_invocation.notify.show_splashscreen (3.5.28) ( Std/Pro )

  Shows the splash screen whenever a second instance is launched.