RP/TUX Tuxedo GWTDOMAIN Process Remains After tmshutdown Utility Completes Successfully

(Doc ID 1600427.1)

Last updated on APRIL 26, 2017

Applies to:

Oracle Tuxedo - Version and later
Linux x86-64


Sometimes a Tuxedo GWTDOMAIN process remains, after executing a Tuxedo tmshutdown command, with the following stack trace.

tmshutdown completes successfully and network port is freed but one GWTDOMAIN thread remains with pthread_cond_signal
This problem is seen on Linux platform only.

Thread 1 (Thread 0x2b3b355ddca0 (LWP 16802)):
#0  0x0000003db100d654 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x0000003db100b47b in pthread_cond_signal@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#2  0x00002b3b3509b92c in _e_thread_cond_signal ()    from /home/tux1111/tuxedo11gR1/lib/libengine.so
#3  0x00002b3b34422324 in gw_toDestroyMgr ()    from /home/tux1111/tuxedo11gR1/lib/libgw.so
#4  0x00002b3b3442261a in thrgw_run_svr ()    from /home/tux1111/tuxedo11gR1/lib/libgw.so
#5  0x0000000000401758 in _tmrunserver ()
#6  0x00002b3b34a6dd2c in _tmstartserver ()    from /home/tux1111/tuxedo11gR1/lib/libtux.so
#7  0x000000000040143d in main ()





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