RP/TUX 6.5, TUX 6.51, TUX 7.1, TUX 8.0 - GWTDOMAIN tight loop (Doc ID 769771.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 6.5., 6.51, 7.1, 8.0
Information in this document applies to any platform

Goal

On some occasions, a GWTDOMAIN process might enter a tight loop at the following place (stack trace produced by killing
the process with SIGABRT):

(dbx) where
current thread: t@1
=>[1] dom_close(_tm_cntxt = 0x24db0, gpnd = 24, flags = 0), line 324 in "gwnw_subs.c"
  [2] _e_net_disconnect(_tm_cntxt = 0x24db0, gpnd = 24, flags = 0), line 744 in "e_net.c"
  [3] pollin(_tm_cntxt = 0x24db0, gpnd = 24), line 1321 in "e_net.c"
  [4] _e_net_handle_event(_tm_cntxt = 0x24db0, gpnd = 24, flags = 0), line 841 in "e_net.c"
  [5] _e_net_run(_tm_cntxt = 0x24db0, timeout = 0, flags = 0), line 4355 in "e_net.c"
  [6] gw_nw_poll(_tm_cntxt = 0x24db0, act_idx = 21), line 58 in "gwnw_poll.c"
  [7] gw_run_svr(_tm_cntxt = 0x24db0), line 74 in "gwsvrrun.c"
  [8] _tmrunserver(flags = 0), line 316 in "gwserver.c"
  [9] _tmstartserver(argc = 15, argv = 0xffbef8ac, tmsvrargs = 0x238f8), line 123 in "tmstrtsrvr.c"

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