Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 8.0, 8.1
Information in this document applies to any platform
With Tuxedo 7.1 and previous, when only one server in one group was involved in an update transaction this would result in a one-phase optmization where ultimately the server itself would call xa_commit(). From Tuxedo 8.0 on however it seems that the commit processing is now systematically performed by the TMS. This behavior seems to add unncecessary overhead in terms of processing and resource consumption, as well as defining the TMS servers as bottlenecks in the architecture.
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