Message-ID: <962814202.1361.1425258105495.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1360_441896904.1425258105494" ------=_Part_1360_441896904.1425258105494 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In theory, only JMS servers supporting XA and providing a
s.XAConnectionFactory implementation can be used with transaction ma=
nagers. In practice, there is a way around this limitation.
The Last Resource Commit optimization (sometimes referred to as Last Res= ource Gambit or Last Agent optimization) allows a single non-XA resource (J= MS server or database) to participate in a XA transaction by cleverly order= ing the resources.=20 =20
To enable it, you just have to create a
code> using the bitronix.tm.resource.jms.lrc.LrcXAConnectionFactory as the implementation.
Here's an example of code configuring a ActiveMQ datasource:=20 =20
and the same example viewed as a Resource Loader configuration=20 =20