Re: Time Required To Abort Transaction After Tuxedo
Transaction Time

Thanks Tod!!!

First, I am able to see that Transaction (pt in tmadmin) in Tuxedo is marked as
TPABORTONLY. After that during my transaction time is being taken by SQL query
called through Pro *c ( In Oracle) and from this query I am getting a database
error code (24761) for which description is "transaction rolled back"
and depending on this database error code I am reporting application error.

On this basis I am on conclusion that Tuxedo is "aborting" this
transaction. My issue is that this whole process (abort mark at Tuxedo, Oracle
error and application error message) is taking around 60-70 seconds after
timeout detection so I need to know is there any governing factor to control
this time as due to this my application is not able to meet one requirement (as
due to this long time I am not able to report error to user and before that due
to network time out my application is aborted and user is not informed on
this).