RP/TUX 6.5, TUX 6.51, TUX 7.1, TUX 8.0 - TMS cannot be shutdown when a timeout occurs and second tmshutdown will hang. (Doc ID 770721.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 19-07-2011***

Goal

When a TMS process is stalled/non-responding for any reason (e.g., artificially bye kill -STOP pid) and if you try to
"tmshutdown -w 5 -y" to force shutdown the Tuxedo system, the TMS will not be shutdown and tmshutdown will
not be completed successfully. You will find 1 or 2 TMS process(es) and BBL reamain after the tmshutdown. Then, if
you try to run the 'tmshudown' again to shutdown the left-behind Tuxedo processes, the tmshutdown will hang forever in
certain circumstances.

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