TUX 6.x, TUX 7.x, TUX 8.x - Request for a global limit on transaction timeouts
(Doc ID 769538.1)
Last updated on MAY 19, 2020
Applies to:Oracle Tuxedo - Version 6.4 and later
Information in this document applies to any platform.
Information in this document applies to any platform
There should be some kind of administrative control over the timeout of the global transactions initiated by clients and/or servers. The objective is to protect a production application from bad development practices such as using infinite or very high transaction timeouts. This feature could be implemented by means of a new environment variable and/or configuration parameter which would define a high limit for any transaction timeout. If a process encountered this variable/parameter set and tried to start a transaction with a higher timeout than the specified by it, the actual value used would be automatically readjusted to the maximum. This feature should work for transactions initiated either by servers or clients (native, /WS, Jolt, ...) This enhancement could be very useful for eLink SNA when the global transaction is initiated on mainframe side (CICS or IMS), because in this case, the timeout is currently infinite on Tuxedo side.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document