ER: Enhancement Request Tuxedo JCA Transactions Time-out Have To Be Managed In The RA.xml
(Doc ID 2053446.1)
Last updated on NOVEMBER 04, 2016
Applies to:Tuxedo JCA Adapter - Version 126.96.36.199.1 and later
Information in this document applies to any platform.
Tuxedo JCA enhancement request: JCA transactions time-out have to be managed in the RA.xml.
There is a need for a parameter to manage easily ,the transaction time-out for all inbound transaction from java server to a Tuxedo domain. The value has to replace the
programming value if this value is greater than the parameter. The goal is to be able for an administrator to set transaction time-out limit ofr all JCA inbound transactions
Based on the JCA documentation :
The CCI TuxedoJCAConnection.getLocalTransaction returns a
TuxedoJCALocalTransaction instance. A client application can then use the
returned TuxedoJCALocalTransaction to demarcate a Tuxedo JCA Adapter local
transaction on the Tuxedo systems.
The local transaction timeout can be specified through the following list in preference order:
begin(int timeoutvalue): Tuxedo JCA Adapter Extension, the timeout valueis in second.
AppManagedLocalTxTimeout: This is a ra.xml property and also specified in second.
com.oracle.tuxedo.adapter.ApplicationManagedLocalTxTimeout: A system property and it is specified as "-Dcom.oracle.tuxedo.adapter.AppManagedTxTimeout=value"
default value: The default local transaction timeout value is 300 seconds.
However, there still is a need to manage only the JCA transactions time-out
when the client code doesn't match the application agreement.
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