RP/TUX 6.5, TUX 6.51, TUX 7.1 - LIBWSC 1034+1032 when ubb(NOTIFY=SIGNAL) on tpcall (Doc ID 769284.1)

Last updated on NOVEMBER 04, 2016

Applies to:

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

Goal

This problem occurred, in case that NOTIFY is set to SIGNAL in the ubbconfig file.
It works well with Tuxedo 6.4.

                      Tux 6.4                                  Tux 6.5(without patch)                     Tux 6.5(with
latest patch(300))
DIPIN             OK                                           OK                                                     
           OK
SIGNAL          OK                                           Not OK                                                   
      Not OK

122244.lcsol7!?proc.5832: LIBWSC_CAT:1034: ERROR: Received unexpected message with opcode 5
122244.lcsol7!?proc.5832: LIBWSC_CAT:1032: ERROR: Failed to receive expected reply
122244.lcsol7!?proc.5832: TRACE:at:  } tpcall = -1 [tperrno TPESYSTEM]
122247.lcsol7!?proc.5832: TRACE:at:  { tpterm()
122247.lcsol7!?proc.5832: LIBWSC_CAT:1034: ERROR: Received unexpected message with opcode 12
122247.lcsol7!?proc.5832: LIBWSC_CAT:1032: ERROR: Failed to receive expected reply  

Test Case:

1. Setting the releated environments
    $. ./setenv
    $tmloadcf -y ubbconfig
2. start Tuxedo
    $tmboot -y
3. run workstation client
    $clt fdsa TOUPPER
     tpinit = 1
     tpcall = 0[]
     tpterm = 1
     tpinit = 1
     tpcall = -1[TPESYSTEM - internal system error]
     tpterm = -1

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