RP/TUX 8.0 - DDR continues to wildcard /TDOMAIN even after configured /TDOMAIN becomes unavailable (Doc ID 771400.1)

Last updated on NOVEMBER 04, 2016

Applies to:

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

Goal

Given a /TDOMAINS configuration which uses data dependent routing to route requests to different domains, if you have
the following configuration:

*DM_ROUTING
FMLROUTE FIELD = INPUT BUFTYPE ="FML32" RANGES = "'aaaaa':DOMAIN1, 'bbbbb':DOMAIN2, *:DOMAIN3"

requests whose data matches 'aaaa' goes to domain1
data match of 'bbbb' goes to domain2
and domain3 is the wildcard range '*'

If domain1 becomes unavailable, requests of 'aaaa' goes to the wildcard domain. The administrator should expect a
TPESYSTEM failure instead because they have configured those requests to go to domain1 and it is unavailable. 
In the current scenario, the administrator loses control over how requests get routed simply because a domain becomes
unavailable.

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