WebLogic Tuxedo Connector Load Balancing Distribution No Longer Even After A Remote Domain Is Offline (Doc ID 2304480.1)

Last updated on SEPTEMBER 19, 2023

Applies to:

Symptoms

Weblogic 12.1.3 WebLogic Tuxedo Connector(also known as WTC) component
Tuxedo 12.1.1

Running normally, WebLogic evenly distributes load to all Tuxedo instances.
After stopping one remote Tuxedo instance all of the load it was handling is redirected to just one of the other Tuxedo instances configured instead of evenly distributing the load to the remaining connected Tuxedo remote domains.

For example:
 1. Start with WebLogic Server (also known as WLS) console with 3 configured WTCImport TOUPPER services each with remote access point lists containing 3 remote Tuxedo domains for fail over
TOUPPER TUXDOM_01,TUXDOM_02,TUXDOM_03
TOUPPER TUXDOM_02,TUXDOM_03,TUXDOM_01
TOUPPER TUXDOM_03,TUXDOM_01,TUXDOM_02
Take TUXDOM_1 offline and see TUXDOM_2 getting 2/3 of the requests

 2. Use the WLS console to change the WTC Import configuration so that there are no fail over domains defined in the WTC Import remote access list
TOUPPER TUXDOM_01
TOUPPER TUXDOM_02
TOUPPER TUXDOM_03
but still see TUXDOM_2 getting 2/3 of the requests

 3. Use the WLS console again to change the WTC Import configuration so that there is fail over and load balancing between TD2+TD3 if TD1 offline
TOUPPER TUXDOM_01,TUXDOM_02
TOUPPER TUXDOM_02,TUXDOM_03
TOUPPER TUXDOM_03,TUXDOM_01
TOUPPER TUXDOM_01,TUXDOM_03
TOUPPER TUXDOM_02,TUXDOM_01
TOUPPER TUXDOM_03,TUXDOM_02
but still see TUXDOM_2 getting 2/3 of the requests

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.