How do you ignore the Term Signals to prevent the Application from Shutting Down? (Doc ID 1911300.1)

Last updated on MAY 11, 2016

Applies to:

Oracle Knowledge - Version 8.1.3.0 and later
Linux x86

Goal

There are scenarios when the application is stopped but prior to that there were no stop commands issued. If you encounter this and you also note Term trapped. Shutting down in your IC Logs

that is an indication a kill command was sent. On Linux systems there can also be backup programs that run as cron jobs that will send out system wide TERM signals that can cause the Wrapper to shutdown.

 

Example Message From Logs:

Thu Jun 05 20:09:55 EDT 2014 - [Session created - Session Count: 82]
TERM trapped. Shutting down.
5-Jun-2014 8:09:56 PM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-abc.com%2F123.456.789.163-8228
5-Jun-2014 8:09:56 PM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-abc.com%2F123.456.789.163-8088
5-Jun-2014 8:09:57 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms