EOEN Messages Stuck in Working Status During Profile Syndication (Doc ID 1944676.1)

Last updated on JANUARY 26, 2024

Applies to:

Symptoms

When running a Syndication of approx 700 profiles, the EOEN messages get stuck in working status.  Second of two EOEN_MSG service operations is sitting in Working for 20 minutes (first one complete almost immediately) until Tuxedo finally reports a SIGKILL errorr, at which point the PSSUBHND_dflt service dies.  The issue also does not occur using processes that fire off a smaller number of messages (e.g. it works fine for 300 profiles). 

The error being reported in TUXLOG is as follows:

 164015.pwrvm43!BBL.10747980.1.0: CMDTUX_CAT:1836: WARN: Server(11993204)
processing terminated with SIGKILL after SVCTIMEOUT
 164015.pwrvm43!BBL.10747980.1.0: LIBTUX_CAT:541: WARN: Server PUBSUB/301
terminated
 164015.pwrvm43!BBL.10747980.1.0: LIBTUX_CAT:557: INFO: Server PUBSUB/301
being restarted
 164015.pwrvm43!restartsrv.15007970.1.-2: 09-20-2014: Tuxedo Version 10.3.0.0,
64-bit
 164015.pwrvm43!restartsrv.15007970.1.-2: CMDTUX_CAT:1850: INFO:
TM_RESTARTSRVTIMEOUT is set to 360 seconds
 164016.pwrvm43!PSSUBHND.10879124.1.-2: 09-20-2014: Tuxedo Version 10.3.0.0,
64-bit
 164016.pwrvm43!PSSUBHND.10879124.1.-2: LIBTUX_CAT:262: INFO: Standard main
starting
 164016.pwrvm43!PSSUBHND.10879124.1.-2: LIBTUX_CAT:476: WARN: Server 98/301:
client process 15073406: lost message
 164016.pwrvm43!PSSUBHND.10879124.1.-2: LIBTUX_CAT:477: WARN:
SERVICE=PSSUBHND_dflt    MSG_ID=0    REASON=server died
 164017.pwrvm43!restartsrv.15007970.1.-2: server PUBSUB/301: CMDTUX_CAT:580:
INFO: A server process has restarted: 10879124

Tracing on the PSSUBHNDLR_dflt shows that the handler process in updating the database involves a component interface interactions, some of which are taking a few minutes per process resulting in long running processing.  

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.