SVCTIMEOUT, tmshutdown -k, And tpkill Cause Tuxedo Bulletin Board Dead Lock LIBTUX_CAT:5005
(Doc ID 2102474.1)
Last updated on DECEMBER 21, 2022
Applies to:
Oracle Tuxedo - Version 6.5 to 12.1.3Information in this document applies to any platform.
Symptoms
When sending SIGKILL to Tuxedo processes, if Tuxedo is running critical section of shared memory(for example, changing the bulletin board tables under lock or unlocking the bulletin board memory area),
bulletin board (also known as BB) corruption may occur and cause unexpected problem. (for example - hang with LIBTUX_CAT:5005, crash and service table corruption)
Tuxedo is sending an operating system SIGKILL to application processes in the following situations (so it should be done carefully):
Service timeout (it reaches to the SVCTIMEOUT configured in the Tuxedo ubbconfig configuration file)
tmshutdown -k KILL
tmshutdown -w timeout
tpkill -9
Changes
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 |
Changes |
Cause |
Solution |
References |