Tuxedo GWTDOMAIN Sometimes Did Not Process Any Request For Some Seconds (Doc ID 1409306.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle Tuxedo - Version 10.3.0 to 11.1.1.2.0 [Release 10gR3 to 11g]
IBM AIX on POWER Systems (64-bit)
HP-UX PA-RISC (64-bit)
HP-UX PA-RISC (32-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
HP-UX Itanium
Oracle Solaris on x86-64 (64-bit)
IBM AIX on POWER Systems (32-bit)
Oracle Solaris on SPARC (32-bit)

Symptoms

We sometimes observe the GWTDOMAIN server did not process any request for some seconds, at most it is 10 seconds. From the stack trace we can find PROC thread is waiting on the mutex lock but the NW thread  is holding the lock.

Stack trace example is as follows:

_mutex_lock(??, ??, ??) at 0x900000000c6e8bc
_e_mutex_lock() at 0x900000001262380
_e_net_freend() at 0x900000001085da8
gw_nw_mk_error() at 0x9000000013c81d4
_dom_msgrcv() at 0x9000000013cf470
gwmsg_domrcv() at 0x900000001556fd8
thrgw_proc_loop() at 0x900000001559a00
__fd_select(??, ??, ??, ??, ??) at 0x9000000001222cc
gpnwssw.select() at 0x900000001089edc
_e_net_poll() at 0x9000000010885a4
_e_net_icursor() at 0x90000000108b9a8
_e_net_opencursor() at 0x90000000108c678
thrgw_nwrecv_loop() at 0x900000001559d20

These two threads may stay this way for at least 10 seconds. It causes the Tuxedo GWTDOMAIN server to not process a request. Another way to say this is that the GWTDOMAIN hangs for some seconds.

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