RP/TUX 10.0 - From time to time after a successful tmhsutdown -y GWTDOMAIN process is still running (Doc ID 778277.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 15-07-2010***

Goal

DESCRIPTION:
If in your dmconfig you defined a dummy node (name cannot be resolved by DNS) with MAXRETRY=MAXLONG and if to start
domain you ran sequence:

tmboot -A
tmboot -y

then after a successful (no error in outpout and ulog file) tmsutdown -y, GWTDOMAIN is still running (still reported
in ps output).

This misbehavior does not occur on each tmshutdown.

IMPACT:
Need to manually kill GWTDOMAIN running process to avoid error while next boot.

CONFIGURATION:
TUXEDO 10.0 32-bit on AIX

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