RP/TUX 6.5, TUX 6.51, TUX 7.1, TUX 8.0, TUX 8.1 - TPNOBLOCK flag does not work with network timeout parameter "-N" in WSL
Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 19-08-2011***
PATCHLEV6.5: 194 COMPONENT:/T If the WSL is configured with the network timeout option (-N), a workstation client will block on tpgetrply(3), even when the TPNOBLOCK flag is set. When a client sets the TPNOBLOCK flag in a tpgetrply(3), the client should return immediately with tperrno TPEBLOCKafter a blocking condition is found. Instead, the client blocks, and when the blocking condition is over, can receive tperrno TPESYSTEM. Without the -N CLOPT, the problem does NOT occur.
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