Why Does The Tuxedo tmshutdown Command, With A "-w" Option, Fail To Shut Down All Tuxedo WSH processes?
(Doc ID 776166.1)
Last updated on MAY 19, 2020
Applies to:Oracle Tuxedo - Version 8.0 and later
Information in this document applies to any platform.
The command "tmshutdown -w<delay> -s WSL" normally shuts down the Tuxedo WSL process as well as its associated WSH processes. The "-w" option allows the BBL to send a SIGTERM and then a SIGKILL to ensure that the shutdown occurs unconditionally.
In some situations, however, the WSHs processes are not shut down as expected.
To reproduce this behavior, boot a WSL process with at least one WSH. Run gdb, and attach to the process ID of the WSL, which will keep the WSL busy. Next, execute "tmshutdown -w3 -s WSL". Notice that the WSL is terminated, but not the WSH.
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