My Oracle Support Banner

WSH Fails To Post .Sysclientdied Event When The Client Is Suspended. (Doc ID 1302604.1)

Last updated on MAY 06, 2024

Applies to:

Oracle Tuxedo - Version 10.3.0 to 10.3.0 [Release 10gR3]
IBM AIX on POWER Systems (64-bit)
HP-UX PA-RISC (64-bit)
Oracle Solaris on SPARC (64-bit)
HP-UX Itanium
x86 64 bit


.SysClientDied event is not posted when an attempt to deactivate a client is performed by setting the T_CLIENT state to SUSpended and then setting its state to DEAd via .TMIB service calls or by terminating it via Ctrl-Del once its status is SUSpended.

Following messages are reported in the ULOG file:

...WSNAT_CAT:1287: WARN: Forced shutdown of client; user name ... client name ...; workstation address ...
...LIBTUX_CAT:1409: ERROR: Suspended client attempting to generate new request
...GP_CAT:1095: ERROR: tppost failed when posting event .SysClientDied, tperrmsg=<TPESYSTEM - internal system error>, dropping the message


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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