Configuration13

bitronix.tm.serverId

serverId

The machine's IP address but that's unsafe for production usage

an ASCII ID that must uniquely identify this TM instance. It must not exceed 51 characters or it will be truncated.

bitronix.tm.2pc.async

asynchronous2Pc

false

Should two phase commit be executed asynchronously? Asynchronous two phase commit will improve 2PC execution time when there are many resources enlisted in transactions but can be very CPU intensive when used on JDK 1.4 without the java.util.concurrent backport implementation available on the classpath. It also makes debugging more complex. See here for more details.

bitronix.tm.2pc.warnAboutZeroResourceTransactions warnAboutZeroResourceTransactions

warnAboutZeroResourceTransaction

true

Should transactions executed without a single enlisted resource result in a warning or not? Most of the time transactions executed with no enlisted resource reflect a bug or a mis-configuration somewhere.

bitronix.tm.disableJmx

disableJmx

false

The transaction manager registers objects in the JMX registry by default if available. Set this to true to never register JMX objects.

bitronix.tm.jndi.userTransactionName

jndiUserTransactionName

java:comp/UserTransaction

The name under which the transaction manager will be bound in the internal JNDI provider.

bitronix.tm.currentNodeOnlyRecovery

currentNodeOnlyRecovery

false in 1.3.2 and earlier
true in 1.3.3 and up

Set this to true if you run multiple instances of the transaction manager on the same JMS and JDBC resources to avoid the recovery process to try to recover transactions started by another node. See here for more details.