Can your transaction manager promise higher availability?
您的事务管理器能保证较高的可用性吗？
Behavior of transaction manager if the resource manager fails.
资源管理器失败时的事务管理器行为。
Useful structures when working with an XA-enabled transaction manager.
使用支持XA的事务管理器时的有用结构。
A process in the transaction manager executes a DB2-related transaction.
事务管理中的一个进程执行一个DB 2相关的事务。
The transaction manager detects an error before starting the transaction.
启动事务前，事务管理器检测到一个错误。
The WebSphere transaction manager then attempts to get a new connection to RAC.
WebSphere事务管理器将尝试获取到RAC的新连接。
The transaction manager can either be a multi-threaded or a multi-process environment.
事务管理器要么是一个多线程环境，要么是一个多进程环境。
The error is that the transaction manager was unable to perform an XA recover operation.
该错误是由于事务管理程序无法执行XA恢复操作。
A distributed transaction involves a transaction manager and one or more resource managers.
一个分布式的事务涉及一个事务管理器和一个或者多个资源管理器。
This article looks at the expected behavior of a transaction manager when a resource manager fails.
本文展示了当资源管理器出故障时，预期的事务管理器行为。
In addition, the application USES a transaction manager to ensure the reliability of data exchange.
此外，应用程序使用事务管理器来确保数据交换的可靠性。
The updates only become hardened once the transaction manager initiates the two-phase commit process.
只有在事务管理器启动两阶段提交进程时，更新才会变得确定。
This example causes the transaction manager process to connect to the database with these parameters.
在此示例中，事务管理器流程使用以下参数连接到数据库。
The transaction manager USES CORBA OTS when an EJB in one container calls an EJB in another container.
当一个容器中的ejb调用另一个容器中的EJB时，事务管理程序将使用CORBAOTS。
This configuration would make Spring automatically pick up your application server's transaction manager.
此配置将使Spring自动选取您的应用程序服务器的事务管理器。
All of these entities interact with the transaction manager so that your application code doesn't have to.
所有这些实体都与事务管理器进行交互，于是应用程序代码就不必与之交互了。
The behavior of the transaction manager should not be affected by the state change of the resource manager.
事务管理器的行为应该不会受到资源管理器状态变化的影响。
The transaction manager asks all the resource managers to prepare to commit recoverable resources (prepare).
事务管理器请求所有资源管理器准备提交可恢复资源(准备)。
This parameter is required to improve performance of DB2 when operating with the particular transaction manager.
在操作特定的事务管理器时，需要此参数来改进DB2的性能。
The transaction manager is expected to finish the transaction when the resource manager becomes available again.
当资源管理器再次恢复可用时，事务管理器需要能够完成事务。
The resource manager fails between prepare and commit processing, and the transaction manager detects the failure.
在准备和提交进程期间，资源管理器出现故障，事务管理器检测到错误。
The transaction manager should be able to detect the availability of the resource manager as it becomes available.
事务管理器应该在资源管理器可用时，能够检测到其可用性。
The transaction manager should be able to continue with transactions that do not involve the failed resource manager.
事务管理器应该能够继续处理没有包含出错资源管理器的事务。
However, the desired behavior of the transaction manager would be the same even if the unit of execution was a thread.
然而，即使执行单元是一个线程，期望的事务管理器行为都是相同的。
This helps ensure the availability of the transaction manager and, to some extent, can help simplify application logic.
这一点有助于确保事务管理器的有效性，并且在一定程度上帮助简化应用程序逻辑。
The transaction manager should be able to resolve the failed transaction when the failed resource manager becomes available.
事务管理器应该能够在出错的资源管理器恢复可用时解决出错的事务。
If a database failure occurs, the transaction manager reports the possibility of inconsistent data from failed transactions.
如果发生数据库故障，则事务管理器将报告故障事务导致的不一致数据的可能性。
The transaction-manager property holds a reference to the transaction manager bean defined in the Spring configuration file.
transaction - manager属性保存一个对在Spring配置文件中定义的事务管理器bean的引用。
Should the transaction manager fail during the commit processing, the transaction may be left in-doubt in the resource managers.
如果在提交过程中事务管理器失败，则事务可能在资源管理器中处于未确定状态。
The unit of work must be managed by an external transaction manager running on the same system as the client business application.
工作单元必须由在客户机业务应用程序所在的系统上运行的外部事务管理器管理。
应用推荐