Configure shutdown behavior

Fast shutdown by file force_stop

You can force the Integration Server to stop. To do this, place a file named force_stop in the installation directory before the stop. The Integration Server then stops running jobs immediately. It marks them as System crash and crashed jobs. The file can be empty (0 KB in size).

As soon as the shutdown starts, the Integration Server deletes this file automatically.

Set the parameter createForceStopFile to true in the configuration file ./etc/startup.xml. The Integration Server then creates the file automatically at every start. Every stop then becomes a fast shutdown.

<Call name="addApplication">
	<Arg>
		<New class="com.ebd.hub.datawizard.app.DataWizardSetup">
			<Call name="setConfiguration">
				<Arg>
					<New class="com.ebd.hub.datawizard.app.DataWizard">
						...
						<Set name="createForceStopFile">true</Set>
						...
						<Set name="createCleanStopFile">true</Set>
						...
					</New>
				</Arg>
			</Call>
		</New>
	</Arg>
</Call>

NOTE  You can also trigger a force stop through the HTTP API. See also: System stop, Load Balancing, DMZ server, profile quickview (REST API).

File clean_stop

Set the parameter createCleanStopFile to true in the configuration file ./etc/startup.xml. The Integration Server then creates the file clean_stop in the installation directory as soon as the server process has stopped.

The Integration Server deletes an existing clean_stop file when it restarts. External applications or scripts can use this feature to evaluate the Integration Server status.

Automatically terminate an incompletely started Integration Server or Lobster Integration

Errors in the XML configuration files can prevent the startup. An occupied port can also prevent the Integration Server or Lobster Integration from starting completely. Error messages then appear, depending on the operating system and startup type. You can find them in the command prompt or in the files ./logs/wrapper.log and ./logs/console.txt.

Set the parameter stopServer to true in the file ./etc/startup.xml. The Integration Server then stops completely and automatically after such an error.

<Call name="addApplication">
	<Arg>
		<New class="com.ebd.hub.datawizard.app.DataWizardSetup">
			<Set name="stopServer">true</Set>
			<Call name="setConfiguration">
				<Arg>
					<New class="com.ebd.hub.datawizard.app.DataWizard">
					...
					</New>
				</Arg>
			</Call>
		</New>
	</Arg>
</Call>

NOTE
The parameter stopServer is expected in the context of the DataWizardSetup class, not in the context of the DataWizard class.
A StorageService access error to persistent storage also triggers an automatic restart with exit code 136. For details, see the StorageService article.