RP/TUX 7.1, TUX 8.1 - After network timeout, next ATMI call fails (Doc ID 772871.1)

Last updated on NOVEMBER 04, 2016

Applies to:

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

Goal

The sequence of call is as follows:
tpinit/tpalloc/tpalloc/tpcall(network timeout)/tpterm. Then tpinit/(tpalloc or tpsetunsol) hangs forever.

The configuration is *RESOURCES NOTIFY SIGNAL, WSL with CLOPT "-N 3", and the simpserv server with sleep(5).
The /WS client , whether using tpinit flag TPU_SIG or 0, whether having an unsolicited message handler or not  will
hang at second loop of calls on Windows.

On UniX, the behavior is that second and following tpinit calls fail with LIBWSC 2003, may be triggered by LIBWSC
1477.

The requested platform is Windows. Not specifying NOTIFY in *RESOURCES, but having tpinit flag TPU_SIG works fine.
Changing USIGNAL has no effect.

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