JBoss.orgCommunity Documentation

Chapter 3. OTS and Java EE Transaction Service Management

3.1. Starting the run-time system
3.1.1. OTS configuration file
3.1.2. Name service
3.1.3. resolve_initial_references
3.1.4. Resolution services supported per ORB
3.2. XA Specific management
3.3. Selecting the JTA implementation

The JBossTS run-time support consists of run-time packages and the OTS transaction manager server. By default, JBossTS does not use a separate transaction manager server. Instead, transaction managers are co-located with each application process to improve performance and improve application fault-tolerance by reducing application dependency on other services.

When running applications which require a separate transaction manager, set the JTSEnvironmentBean.transactionManager environment variable to value YES. The system locates the transaction manager server in a manner specific to the ORB being used. This method may be any of:

You override the default registration mechanism by using the OrbPortabilityEnvironmentBean.resolveService environment variable, which takes the following values:

Resolution MechanismORB
OTS configuration fileAll available ORBs
Name ServiceJacORB

Each XA Xid that JBossTS creates must have a unique node identifier encoded within it. JBossTS only recovers transactions and states that match a specified node identifier. Provide the node identifier with the CoreEnvironmentBean.nodeIdentifier property. This value must be unique across your JBossTS instances. If you do not provide a value, JBossTS generates one and reports the value via the logging infrastructure.

When running XA recovery, you need to specify which types of Xid JBossTS can recover. Use the JTAEnvironmentBean.xaRecoveryNodes property to provide one or more values, in a space-separated list.

Two variants of the JTA implementation are now provided and accessible through the same interface. These are:

Both of these implementations are fully compatible with the transactional JDBC driver provided with JBossTS.