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 2.x.x</h1>

<p>BTM 2.x.x is a cleaned up and refined version of the 1.3.x branch with no major change visible from the end user. A lot of internal polishing happened enabling future developments as well as the usual bug fixes and some requested new features.</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>JDBC 4 support</h3>

<ul>
	<li>BTM can now be built against JDBC 4 API and its JDBC connection pool now has support for the isValid() connection check instead of the test query when a JDBC 4 driver is detected. Set enableJdbc4ConnectionTest property to true to enable this feature. The pool will then autodetect if the underlying JDBC driver is compatible and use the feature if available, otherwise it will revert back to the old test query mechanism.</li>
</ul>

<h3>JDBC custom isolation level</h3>

<ul>
	<li>The JDBC connection pool can now force connections to a specific isolation level. Set the PoolingDataSource isolationLevel property to one of these values: READ_UNCOMMITTED READ_COMMITTED REPEATABLE_READ SERIALIZABLE to force the level you want.</li>
</ul>

<h3>Support for per connection transaction affinity</h3>

<ul>
	<li>BTM's pool can now track connections requested from the pool and return the same connection for every DataSource.getConnection() call in the same transaction. Set shareTransactionConnections property on your pool to enable this feature.</li>
</ul>

<h3>Improved JDBC PreparedStatement cache</h3>

<ul>
	<li>The JDBC PreparedStatement cache is now much more efficient than it used to be as well as being much more robust.</li>
</ul>

<h3>JTA 1.1 support</h3>

<ul>
	<li>The JTA 1.1 TransactionSynchronizationRegistry has been implemented and can now be used. It can be acquired either via the TransactionManagerServices singleton or via the embedded JNDI server under the (configurable) java:comp/TransactionSynchronizationRegistry standard name.</li>
</ul>

<h3>Improved JMX monitoring</h3>

<ul>
	<li>The JMX monitoring beans have been extended for better monitoring capabilities, particularly for the JMS and JDBC connection pools.</li>
</ul>

<h3>Improved Maven 2 support</h3>

<ul>
	<li>The published POM has been updated to depend on the standard JTA 1.1 JAR instead of the Geronimo JTA 1.0.1B one which is more commonly found. Sources and javadocs are now also uploaded to the central maven 2 repo. Tomcat and Jetty lifecycle JARs made their way to the maven 2 repo too.</li>
</ul>