Tuxedo tpcall() Via Tuxedo's Domain Protocol Gets Slow Response If Remote Domain Is Not Available
Last updated on AUGUST 29, 2017
Applies to:Oracle Tuxedo - Version 6.4 and later
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Tuxedo domains on Solaris having many(over 40) remote Tuxedo access points defined with Tuxedo ON_DEMAND connection policy configured (in Tuxedo domain configuration file).
The client domains sending a tpcall(), including WebLogic Tuxedo Connector ones, seem to depend on the platform's operating system(also known as OS) configuration.
Usually, if a remote Tuxedo GWTDOMAIN process is not up(but OS is booted) , a Tuxedo tpcall() will get TPESVCERR immediately. If over 40 tpcall() occur, per each domain accesspoint call at the same time, some calls have a resulting delay of 3 seconds.
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