RP/TUX Tuxedo 11gR1PS1 (188.8.131.52.0) WSL Server Crashes After Setting NEW To TA_SUSPENDED And Back To NONE
Last updated on APRIL 26, 2017
Applies to:Oracle Tuxedo - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When using MIB for T_WSL class to suspend the workstation listener (also known as WSL) network, after unsuspended , WSL will crash or will not be able to connect to the WSL process.
Here is definition and reproduce sequence:
WSL SRVGRP=GROUP1 SRVID=999 CLOPT="-A -- -n //server:3333"
ud32 with following script to suspend WSL
After suspended WSL, ud32 with following script to unsuspend WSL
After back to TA_SUSPENDED to NONE, WSL will be crashed with follows:
ff3b09c4 memcmp (0, 0, 4dce0, 4, 2, 1) + 38
ff1e4244 _tmstartserver (0, 0, 38af8, 1f160, 39148, 1f160) + 2f0
00014788 _start (0, 0, 0, 0, 0, 0) + 108
On HP-UX, WSL will not be crashed , but after unsuspended, tpinit() still fails with following error:
145305.server!WSL.27038.1.0: WSNAT_CAT:1190: INFO: Reestablished network address`
145319.server!WSH.27040.1.0: WSNAT_CAT:1372: ERROR: Received message with invalid size -765580672
145321.server!?proc.27073.1.0: 09-25-2013: Tuxedo Version 220.127.116.11.0, 64-bit
145321.server!?proc.27073.1.0: LIBWSC_CAT:1032: ERROR: Failed to receive expected reply
145321.server!?proc.27073.1.0: LIBWSC_CAT:2003: ERROR: Unable to get reply to gssapi token message
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