Tuxedo tmshutdown Command, On A GWTDOMAIN Server, Hangs In msgsnd() On Windows Platform (Doc ID 2150338.1)

Last updated on MAY 05, 2017

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)

Symptoms

 On Windows platform, sometimes a Tuxedo tmshutdown command hangs in msgsnd() when shutting down a Tuxedo GWTDOMAIN server process
The stack trace is :

00 000007fe'fd3e10dc : 00000000'00490000 00000000'7721e256 00000000'0000010000000000'02a08370 : ntdll!NtWaitForSingleObject+0xa
01 00000000'60d7ee6a : 00000000'02a04278 00000000'00000003 0000b5ea'0000000000000000'000001e0 : KERNELBASE!WaitForSingleObjectEx+0x79
02 00000000'60d82a41 : 00000000'000003ff 00000000'02a04278 00000000'0049874000000000'60d7222a : LIBENGINE!stop_interruptible+0x6a
*** ERROR: Symbol file could not be found. Defaulted to export symbols for libtux.dll -
03 00000000'6023f1db : 00000000'00687160 00000000'00000255 00000000'02a0427800000000'00000000 : LIBENGINE!e_ipc_msgsnd+0x51
04 00000000'60163345 : 00000000'00000000 00000000'00677250 00000000'006cdd1000000000'00677250 : libtux!tmmbsendm+0x51b
05 00000000'6017e210 : 00000000'00000000 00000000'02a02eb0 00000000'0800002000000000'00000000 : libtux!tmmsgsnd+0x6d5
*** ERROR: Module load completed but symbols could not be loaded for tmshutdown.exe
06 00000001'40008c62 : 00000000'00000000 00000000'02a02eb0 00000000'0067725000000000'00000000 : libtux!tmmetasnd+0x270
07 00000001'4000a489 : 00000000'00000000 00000000'00677250 00000000'006c5b4000000000'00000000 : tmshutdown+0x8c62
08 00000001'4000e9b6 : 00000000'00677250 00000000'00000002 00000000'0000000300000000'0067ad70 : tmshutdown+0xa489
09 00000001'400146a2 : 00000000'00000000 00000155'5802f619 00000000'0000000000000000'00000000 : tmshutdown+0xe9b6
0a 00000000'76fc652d : 00000000'00000000 00000000'00000000 00000000'0000000000000000'00000000 : tmshutdown+0x146a2
0b 00000000'771fc521 : 00000000'00000000 00000000'00000000 00000000'0000000000000000'00000000 : kernel32!BaseThreadInitThunk+0xd
0c 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'0000000000000000'00000000 : ntdll!RtlUserThreadStart+0x1d

 msgsnd() is waiting for the lock, but message queue is not full.

This problem caused using a very high-spec machine.

Changes

 

Cause

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