RP/TUX 8.1/TUX 9.1 - T_TLISTEN class reports information only about the DEFAULTNET NETGROUP (Doc ID 776905.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 8.1,9.1
Information in this document applies to any platform

Goal

DESCRIPTION:
In an MP configuration with multiple netgroups, the T_TLISTEN class appears to report only the status of the DEFAULT
netgroup.

For example, in a Tux 8.1 MP configuration (any OS platform)  with

  *NETGROUPS
  DEFAULTNET  NETGRPNO=0    NETPRIO=100
  ETH1        NETGRPNO=1200 NETPRIO=50

  *NETWORK
  SITE1 NETGROUP=DEFAULTNET NADDR="//host1:20777" NLSADDR="//host1:20888"
  SITE1 NETGROUP=ETH1 NADDR="//host1a:20777" NLSADDR="//host1a:20888"

and 1 tlisten process started for each netgroup, a GET T_TLISTEN request returns

TA_ERROR    0
TA_MORE 0
TA_OCCURS   2
TA_CLASS    T_TLISTEN
TA_STATE    ACTIVE
TA_STATE    ACTIVE
TA_LMID SITE1
TA_LMID SITE1

If the ETH1 tlisten is killed, GET T_TLISTEN returns exactly the same result:

TA_ERROR    0
TA_MORE 0
TA_OCCURS   2
TA_CLASS    T_TLISTEN
TA_STATE    ACTIVE
TA_STATE    ACTIVE
TA_LMID SITE1
TA_LMID SITE1

If the DEFAULTNET tlisten is killed and ETH1 tlisten is running, GET T_TLISTEN returns

TA_ERROR        0
TA_MORE 0
TA_OCCURS       2
TA_CLASS        T_TLISTEN
TA_STATE        INACTIVE
TA_STATE        INACTIVE
TA_LMID SITE1
TA_LMID SITE1

even though the ETH1 tlisten is running.

Thus, it appears that the T_TLISTEN class reflects the status of the DEFAULTNET group only.  In addition, the
T_TLISTEN class does not define a TA_NETGROUP attribute, which would allow multiple tlisten instances on the same host
to be distinguished.

CONFIGURATION:
Tuxedo 8.1

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