Show Table of Contents
8.5. Local versus distributed transactions
Local Transactions
A Local Transaction allows resource enlistment at only one JVM and does not span across multiple process instances (i.e., VMs). However a separate client JVM may still manage transaction boundaries (begin/commit/rollback) for the JTA. Databases and message queues running as separate processes may still be enlisted as XAResources provided they have drivers that support this.
Distributed Transactions
A transaction is considered to be distributed if it spans multiple process instances, i.e., VMs. Typically a distributed transaction will contain participants (e.g., XAResources) that are located within multiple VMs but the transaction is coordinated in a separate VM (or co-located with one of the participants).
JBossTS provides both local and distributed transactions. If your architecture requires distributed transactions then you should consider using either the JTS implementation from JBossTS, which uses CORBA for communication, or the Web Services transactions component, which uses SOAP/HTTP. Although the JTS/XTS component can be used with JBoss Enterprise Application Platform, it is not a supported part of the platform.
Note
JTS and XTS components are not supported for JBoss Enterprise Application Platform 4.x
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.