Configure Integration Server Shutdown Timeouts in systemd and Tanuki Service Wrapper (RHEL 7+, SLES12+, systemd)

If the regular shutdown time of Integration Server exceeds the configured timeout values for the Tanuki Service Wrapper or systemd, then its daemon will be aborted (SIGKILL, kill -9). The same can happen for any other Software AG daemon. If you have identified such an issue, you need to stop the daemon and manually configure higher timeout values for Tanuki and systemd. The example below shows how to take these actions for Integration Server.

Note:
If you later re-register the daemon with daemon.sh, this manual change gets reset back to the default.

For Tanuki, edit the custom_wrapper.conf file for the Integration Server instance, change the property for shutdown timeout to 500 seconds:

$ vi /opt/softwareag/profiles/IS*/configuration/custom_wrapper.conf
wrapper.shutdown.timeout=500

For systemd, stop the service, identify and edit the service file, add a shutdown timeout of 500 seconds and activate the service by starting the daemon:

# systemctl stop sagis1105
# daemon.sh -L
/usr/lib/systemd/system/sag2is1105.service /opt/softwareag/profiles/
IS_default/bin/sagis105
/usr/lib/systemd/system/sag2spm105.service /opt/softwareag/profiles/SPM/
bin/sagspm105
/usr/lib/systemd/system/sagnserverdaemon.service /opt/softwareag/
UniversalMessaging/server/umserver/bin/nserverdaemon
# vi /usr/lib/systemd/system/sag2is1105.service
TimeoutStopSec=500 <<< add/change this property in the [Service] section.
# systemctl daemon-reload
# systemctl start sagis1105