Tuxedo (All versions): /WS Client Cannot Connect, tpinit() Hangs or Fails (Doc ID 774459.1)

Last updated on NOVEMBER 29, 2016

Applies to:

Oracle Tuxedo - Version 6.5 to 11.1.1.1.0
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 06-10-2014***

Goal

DESCRIPTION:

A /WS client process fails to connect to a Tuxedo application.  Various symptoms are possible, depending on the Tuxedo release, OS, and OS configuration.  For example, the client may hang indefinitely in tpinit().  Alternatively,
tpinit() may fail with TPESYSTEM.  Sometimes there are no messages in the ULOG, either client-side or server-side.  In other circumstances the client may log messages such as the following:


LIBWSC_CAT:1037: ERROR: Network message receive failure
LIBWSC_CAT:1511: ERROR: Did not get diffie-hellman return package
LIBWSC_CAT:1055: ERROR: Unable to establish WSL connection
LIBWSC_CAT:1024: ERROR: Unable to connect to WSH
LIBWSC_CAT:1020: ERROR: Unable to obtain authentication level
The failures may occur more frequently if the WSL's multiplexing factor (-x option) is high.

Typically, the problem does not persist and subsequent /WS clients connect successfully.

CONFIGURATION:
Tuxedo (All versions)

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