RP/TUX 6.5, TUX 6.51, TUX 7.1- Service timeout CHANGES DYNAMICALLY when there is MIB activity (Doc ID 768067.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 6.5, 6.51, 7.1
Information in this document applies to any platform

Goal

When using Tuxedo 6.5 on Sequent / Dynix 4.4.4 machines with 4-8 CPUs, as an example, an MIB request was performed by a
customer as follows:

"Each time a service request is made, the client's details from the MIB are obtained and used in our
infrastructure.

When the system isn't busy, they don't see the SVCTIMEOUT problem because the MIB activity isn't very high.  BUT
during greater loads the MIB activity increases because there are more service requests."

THE PROBLEM is that the SVCTIMEOUT appears to be getting changed randomly and causing services to timeout, and the BBL
to KILL SERVERS!
The busier the system, the worse the problem.

This problem also can occur on Tuxedo 7.1.

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