Compatibility :	3.5.0
Editions :
Platforms :

This property defines the behaviour of the Wrapper if any general error occured. Except for the premapped error (see below).

The user can specify the Wrapper either :

• to SHUTDOWN itself if the Network Drive couldn't be mounted
• or to CONTINUE its process and start the JVM.

The default value is CONTINUE.

wrapper.share.1.startup.failure=CONTINUE

Compatibility :	3.5.0
Editions :
Platforms :

This property specifies what the Wrapper will do if a share couldn't be mounted because the Network Resource already existed.

Please note that the behaviour of the Wrapper for this error is not covered in the wrapper.startup.<n>.startup.failure properties. This was made on purpose in order to provide a way to run the Wrapper as console & service with the same configuration file.

The user can specify the Wrapper either :

• to SHUTDOWN itself if the Network Drive already exists
• or to CONTINUE its process and start the JVM.

The default value is CONTINUE.

wrapper.share.1.startup.premapped=CONTINUE

Compatibility :	3.5.0
Editions :
Platforms :

This property defines how many times the Wrapper should try to mount a Network Drive, if an network based error has occured.

If the Wrapper couldn't mount the Network Drive at the maximum times of retries, the wrapper.startup.<n>.startup.failure property will specify how the Wrapper will proceed.

The default value is "5 times". The Wrapper will try 5 times to mount a Network Drive before giving up.

wrapper.share.1.startup.max_retries=5

Compatibility :	3.5.0
Editions :
Platforms :

This property specifies the interval in seconds the Wrapper will wait until it retries to mount a Network Drive.

The default value is "10 seconds". The Wrapper will wait for 10 seconds until it retries to mount.

wrapper.share.1.startup.retry_interval=10