Diese Eigenschaft definiert das Verhalten des Wrappers, wenn irgendwelche allgemeine Fehler aufgetreten sind. Mit Ausnahme des Premapping-Fehlers (sehen Sie bitte unten).

Der User kann den Wrapper entweder wie folgt:

• auf SHUTDOWN spezifizieren, wenn das Netzwerklaufwerk nicht gemountet werden konnte
• oder auf CONTINUE seines Prozesses und Starten der JVM.

Der Standardwert ist CONTINUE.

wrapper.share.1.startup.failure=CONTINUE

Diese Eigenschaft spezifiziert, was der Wrapper tun wird, wenn eine Freigabe nicht gemountet werden konnte, weil die Netzwerkressource bereits bestand.

Bitte beachten Sie, dass das Verhalten für diesen Fehler in den wrapper.startup.<n>.startup.failure-Eigenschaften nicht abgedeckt wurde. Dies wurde absichtlich gemacht, um einen Weg bereitzustellen, den Wrapper als eine Konsole & Dienst mit der gleichen Konfigurationsdatei auszuführen.

Der User kann den Wrapper entweder:

• auf SHUTDOWN spezifizieren, wenn das Netzwerklaufwerk bereits besteht
• oder auf CONTINUE, um seinen Prozess fortzuführen und die JVM zu starten.

Der Standardwert ist SHUTDOWN.

wrapper.share.1.startup.premapped=CONTINUE

Kompatibel :	3.5.52
Editionen :
Betriebssysteme :

This property specifies the interval in seconds the Wrapper will wait until it retries to mount a Network Drive in the background after startup. This is the interval that the Wrapper will keep trying even after the application has started. It will keep trying until successfully mapped, or a permanent failure is detected.

Continuing to try and mount in the background can be useful in cases where the share server is down when the service is started, but not critical to the application.

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

wrapper.share.1.background.retry_interval=60

Kompatibel :	3.5.52
Editionen :
Betriebssysteme :

This property allows to specify a certain action to be performed whenever a share is successfully mounted after application startup.

This can be useful to trigger a JVM restart, for example, when the application needs to reinitialize itself now that the share is available.

The default action is specified as NONE to do nothing.

wrapper.share.1.background.success.action=RESTART

The full list of actions can be viewed on this page, but the most commonly used are the following:

• DEBUG :

  will cause a debug message to be logged. This is only really useful in helping to understand when the action is fired.

• RESTART :

  will stop the current JVM and then restart a new invocation.

• USER_<n> (Professional Edition) :

  will cause a user defined event to be fired. This can be either the sending of an email, or the execution of an external system command. The command could be anything from performing clean up operations to raising an SNMP trap.

• NONE :

  is useful because it will prevent any triggers with a higher number from being triggered.

Kompatibel :	3.5.52
Editionen :
Betriebssysteme :

This property allows to specify a certain action to be performed whenever a share fails to be mounted after application startup, in a permantent way. This includes incorrect credentials, or mount points. Temporary problems, like a failure to resolve the host name or connect to the server, will continue to be retried in the background.

The property controls what happens when a failure happens in background mode. At this point, the application has already been started despite the share failing to be mapped during startup. So it is generally not a good idea to SHUTDOWN or take some other fatal action at this point. This property can be useful to run USER_<n> actions, or log a message.

The default action is specified as NONE to do nothing.

wrapper.share.1.background.failure.action=USER_1

The full list of actions can be viewed on this page, but the most commonly used are the following:

• DEBUG :

  will cause a debug message to be logged. This is only really useful in helping to understand when the action is fired.

• SHUTDOWN :

  will stop the JVM as well as the Wrapper. Be careful when using this value as a failure to mount a share in the background can occur at any time while the application is already running. If this happened, it would cause your application and the Wrapper to stop.

• USER_<n> :

  will cause a user defined event to be fired. This can be either the sending of an email, or the execution of an external system command. The command could be anything from performing clean up operations to raising an SNMP trap.

• NONE :

  is useful because it will prevent any triggers with a higher number from being triggered.