BTM 1.3.3 released

[Ludovic Orban]

Hi,

BTM 1.3.3 has finally been released after a year of incubation. This release fixes many different small issues and some early design mistakes.

The release can be downloaded here:
 http://docs.codehaus.org/display/BTM/Download

and the Maven2 artifacts and POM have been uploaded in the central Maven2 repository and should ba available shortly.

Following are the release notes:

 Bugs fixed in final release
 ---------------------------
* BTM-55   NPE in PoolingConnectionFactory.java:137 after a createRecoveryXaResourceHolder() did fail on a JmsConnection

 Changes in final release
 ------------------------
* Fixed race condition in JMS pool
* Upgraded SLF4J to version 1.5.8
* BTM now maps the transaction's GTRID to the logger's MDC when available

 Changes in RC2
 --------------
* improved JndiXAConnectionFactory to allow setting urlPkgPrefixes property (required for HortnetQ support)
* fixed leftover bug from BTM-44
* more tests have been added

 Changes in RC1
 --------------
* Refactored the recoverer to implement a much safer algorithm.
* Background recoverer is now enabled by default and configured with the new property Configuration.backgroundRecoveryIntervalSeconds.
  The backgroundRecoveryInterval property has been depecated.
* Resources which cannot be recoverer during startup now don't prevent the transaction manager from starting up but are simply marked
  as 'failed'. Failed resources cannot be used and are automatically retried by the background recoverer.
  This supercedes the 'retryUnrecoverableResourcesRegistrationInterval' configuration property which has been removed.
* 'currentNodeOnlyRecovery' is now enabled by default (see http://docs.codehaus.org/display/BTM/ImplementationDetails#ImplementationDetails-currentNodeOnlyRecovery).
  The recoverer now logs some INFO message when some XIDs have been skipped because this feature is enabled.
* Fixed race conditions in the asynchronous 2PC engine.

 Bugs fixed in RC1
 -----------------
* BTM-33   race condition: potential connection leak when closing connection after transaction terminated
* BTM-34 IllegalArgumentException and MBean exceptions on constraint violation
* BTM-37 Tomcat LifecycleListener shutting down TM too early
* BTM-38 NPE in IncrementalRecoverer
* BTM-39 Improper HeuristicMixedException
* BTM-41 JNDI Context (BitronixContext) returns null rather than NameNotFoundException
* BTM-42 bitronix-scheduler is recreated/restart
* BTM-43 Fix for BTM-33 leads to another problem
* BTM-44 TransactionLogRecord does not get updated when modified, leading to transaction log corruption
* BTM-45 potential NPE in Recoverer.run
* BTM-46 Fall back to current class loader when thread context loader fails (support OSGi)
* BTM-47 improve unrecoverable resource registration retrial and recoverer implementation
* BTM-48 change currentNodeOnlyRecovery default value to true
* BTM-49 Suspend/resume not working as expected
* BTM-50 Improve JndiXAConnectionFactory in order to be able to use SonicMQ


As usual, please report any bug / question / remark / extra wish you might have here.

Thanks and enjoy,

The BTM Team

[Frederic Conrotte]

I'm using BTM with JBoss. I just upgraded to v1.3.3 and ran regression tests, everything seems to work as expected.

Thanks !

[James House]

Thanks a bunch, for a great product Ludovic!


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Ludovic Orban]

It's been my pleasure, I really enjoy working with such a dedicated community.

I once again hope I'll manage to make releases of shorter cycles but only time will tell...