Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<h1>What is new in BTM version 1.3</h1>

<p>BTM underwent many changes for version 1.3. Here is a short summary of what's new and noteworthy.</p>

<h4>Contents</h4>
<img class="editor-inline-macro" src="/plugins/servlet/confluence/placeholder/macro?definition=e3RvYzptYXhMZXZlbD0zfG1pbkxldmVsPTJ9&amp;locale=en_GB&amp;version=2" data-macro-name="toc" data-macro-parameters="maxLevel=3|minLevel=2">

<h2>New Features</h2>

<h3>JNDI provider</h3>

<ul>
	<li>The new JNDI provider and the new <code>jndiUserTransactionName</code> config property.</li>
</ul>

<h3>Journal</h3>

<ul>
	<li>The new Null journal and the related <code>journal</code> config property.</li>
</ul>

<h3>Recoverer</h3>

<ul>
	<li>Incremental recovery.</li>
</ul>

<h3>Resource loader</h3>

<ul>
	<li>The <code>bitronix.tm.resource.bind</code> property is now useless and has been removed.</li>
	<li>Resource creation failures don't block the transaction manager startup anymore and can be retried in the background witht he new <code>retryUnrecoverableResourcesRegistrationInterval</code> config property.</li>
</ul>

<h3>Transaction manager</h3>

<ul>
	<li>No shutdown hook is registered anymore.</li>
	<li>Handling of unilateral resources rollback.</li>
	<li>Transaction termination can be directly controlled, no more need to use the TransactionManager interface.</li>
	<li>Per-resource timeout.</li>
	<li>Transactions are now marked as rollback only when a timeout happens.</li>
	<li>The new resources ordering algorithm and the new <code>twoPcOrderingPosition</code> resource bean property.</li>
	<li>The removal of the <code>bitronix.tm.timer.transactionRetryInterval</code> config property.</li>
</ul>

<ul>
	<li>JMX can be disabled with the new <code>disableJmx</code> config property.</li>
</ul>

<h2>Integration</h2>

<h3>Tomcat 5.5.x / 6.x</h3>

<ul>
	<li>A new class that plugs into Tomcat to maintain BTM's lifecycle (ie: startup / shutdown): <a class="confluence-link unresolved" data-filename="btm-tomcat55-lifecycle.jar" data-linked-resource-default-alias="btm-tomcat55-lifecycle.jar" href="#">btm-tomcat55-lifecycle.jar</a>. Copy the jar to the $TOMCAT_HOME/server/lib folder then edit $TOMCAT_HOME/conf/server.xml and add this below the other lifecycle listeners: &lt;Listener className=&quot;my.package.BTMLifecycleListener&quot; /&gt;</li>
</ul>

<h3>Jetty 6.x</h3>

<ul>
	<li>A new class that plugs into Jetty to maintain BTM's lifecycle (ie: startup / shutdown): <a class="confluence-link unresolved" data-filename="btm-jetty6-lifecycle.jar" data-linked-resource-default-alias="btm-jetty6-lifecycle.jar" href="#">btm-jetty6-lifecycle.jar</a>. Register it in your jetty.xml with a &lt;Call name=&quot;addLifeCycle&quot;&gt; tag.</li>
</ul>

<h2>Upgrading from version 1.2</h2>

<h3>Checklist</h3>
<ul>
	<li>Old resource creation mechanism (ResourceBean.createResource()) has been removed.</li>
	<li>Get rid of the <code>bitronix.tm.resource.bind</code> property in the resource loader's config file if present.</li>
	<li>Get rid of the <code>bitronix.tm.timer.transactionRetryInterval</code> config property if set.</li>
	<li>Make sure you manually shutdown the transaction manager.</li>
	<li>CryptoEngine moved to bitronix.tm.utils package.</li>
</ul>