Tuxedo Domains, With DDR And Domains Link-Level Failover Configured, Do Not Failover When The OS Can't Resolve Host Name of Primary Remote Domain. (Doc ID 1530290.1)

Last updated on DECEMBER 13, 2016

Applies to:

Oracle Tuxedo - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

When the Tuxedo domain gateway has Data Dependent Routing (DDR) configured with Domains Link-Level Failover, if the primary address contains a host name that doesn't exist in DNS, the domain gateway will fail to connect to the primary address, and will not attempt to connect to secondary remote gateways. The following errors can be seen in the Tuxedo userlog:

 

074430.mylocal!GWTDOMAIN.19544.4.0: GP_CAT:1285: ERROR: Can't resolve host name in address //myremotehost.mycompany.net:10001
074430.mylocal!GWTDOMAIN.19544.4.0: LIBGWT_CAT:1303: ERROR: Network error occurred during connection establishment
074430.mylocal!GWTDOMAIN.19544.4.0: LIBGWT_CAT:1512: ERROR: Unable to connect to remote domain MY_REMOTE_DOM
074430.mylocal!GWTDOMAIN.19544.4.0: LIBGWT_CAT:1037: ERROR: Unrecoverable error occurred on send of data - sending failure reply locally

 

The Tuxedo client then fails with TPESVCERR. 

Changes

 The problem can happen when a computer is removed from the network.  If the host name is removed from DNS, but left in the Tuxedo domain configuration, Tuxedo will attempt to use an undefined host name during connection establishment.  The problem can also be caused if you mistakenly configure a host name that is undefined in DNS within a listen address. 

Cause

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