Multithread OCI Application With Own Signal Handler some times does not catch the Signals like SIGTERM Leading to Crash
(Doc ID 3077668.1)
Last updated on MARCH 19, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 19.20.0.0.0 and laterInformation in this document applies to any platform.
OCI Multithreaded Application
Symptoms
The multithreaded OCI application after it connects to DB, it is observed that it starts an extra Oracle-related thread. This thread is observed to be catching signals like SIGTERM sometimes. This creates a problem for programs with its own signal handler because this thread may handle SIGTERM signal, causing the natural reaction to crash the application/process.
The stack of this extra Oracle thread and SigBlk mask indicating signals being blocked are shown below.
The main complaint here is that extra thread handles the signals for the program as Linux (or any Unix variants) randomly chooses one thread to handle the signal raised and it is observed that sometimes it picks this extra thread to handle that signal.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |