RP/TUX 6.5, TUX 6.51, TUX 7.1, TUX 8.0 - /WS client loops with errors in the ULOG when timeout with NOTIFY=SIGNAL (Doc ID 766154.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 6.5, 6.51, 7.1, 8.0
Information in this document applies to any platform

Goal

COMPONENT: /WS
PLATFORM: NT 4.0, WIN 95/98

A workstation client on a Windows platform goes into an infinite loop, and floods the disk with userlog messages,
after being timed out by the workstation handler. This problem can occur under the following conditions.

(1)  The ubbconfig *RESOURCES section has NOTIFY=SIGNAL 
(2)  The WSL has the [-T client-timeout] configured in the CLOPT parameter
(3)  The client is running on Windows NT/95/98
(4)  The client-timeout expires, and the WSH disconnects the client from Tuxedo.  

When the problem occurs, the client loops infinitely, and fills up the userlog with the following messages:

153242.MACH1!?proc.-431615: LIBWSC_CAT:1085: ERROR: Unable to get reply to unsolicited message request
153242.MACH1?proc.-431615: LIBTUX_CAT:1099: ERROR: Cannot process a message with an unknown release, 46
153242.MACH1?proc.-431615: LIBWSC_CAT:1037: ERROR: Network message receive failure

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