RP/TUX 8.1,10.3 - Even With Tuxedo TM_GW_TRAN_ROUTE Environment Variable Set The JOLT Calls Don't Use Same Gateway
Last updated on JANUARY 19, 2018
Applies to:Oracle Tuxedo - Version 8.1 to 10.3.0
Information in this document applies to any platform.
DESCRIPTION: Customer deploys a new Jolt 8.1 application that in the same transaction does several calls to different Tuxedo services.
Environment variable TM_GW_TRAN_ROUTE is configured in the first domain (where Tuxedo JSL/JSH is configured) in order to force that all the calls inside a transaction are routed through the same gateway. However, when the client makes calls to TOUPPER and TOLOWER in a single transaction, some of the calls go through DOMD1 and other through DOMD2. CONFIGURATION: Tuxedo 8.1 RP265 on Solaris 8-9 (32 bits)
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