Why Tuxedo TMS Process Is IDLE Even Though There Are Some Messages In The Queue?

(Doc ID 1907427.1)

Last updated on APRIL 27, 2017

Applies to:

Oracle Tuxedo - Version 9.1 and later
Information in this document applies to any platform.

Goal

Sometimes XA functions take long time, there is one IDLE Tuxedo transaction manager server (also known as TMS) process, but the TMS queue has some messages it it(which may mean that the request is not sent to the IDLE TMS):

> psr
Prog Name      Queue Name  Grp Name    ID   RqDone  Load Done    Current Service
------------   ----------  --------    --   ------  ---------    ---------------
BBL            198743      SITE1        0        2        100    (  IDLE )
TMS            GRP1_TMS    GRP1     30001        0          0    (  IDLE )
TMS            GRP1_TMS    GRP1     30002        0          0    (  IDLE )
TMS_NULL       GRP2_TMS    GRP2     30001        0          0    (  IDLE )
TMS_NULL       GRP2_TMS    GRP2     30002        0          0    ..TMS

> pq
Prog Name      Queue Name  # Serve  Wk Queued  # Queued   Ave. Len    Machine
---------      -------------------  ---------  --------   --------    -------
BBL            198743            1          0         0        0.0    SITE1
TMS            GRP1_TMS          2          0         0        0.0    SITE1
TMS_NULL       GRP2_TMS          2         100        2        0.0    SITE1

 

As TMS servers use multi-server-single-queue(also known as MSSQ) set configuration, why the IDLE TMS can not take queued message?

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