RP/TUX 8.0, TUX 8.1 - gpnet APIs return bad WSAGetLastError in debug mode

(Doc ID 772601.1)

Last updated on NOVEMBER 04, 2016

Applies to:

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

Goal

Difficulty making an MP application boot in MP mode + NWDBG=100 (WinNt being the slave). The reason is that the
BSBRIDGE performs some socket recv in non-blocking mode and expects WSAEWOULDBLOCK errors, not 133 errors, when
calling WSAGetLastError(). It closes the socket and boot fails dirty.

Going deeper, the recv api did return -1 with WSAGetLastError()=133, but this errorcode is put in the NWERRNO(gpnd)
after some E_NET_DBG that breaks the errno obviously. Also the E_NET_DBG traces don't report the errno, which is
useful.

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