Roadmap

Unreleased versions

Version 2.2.0

Planned release date: ???

Planned new features and bug fixes:

Version 2.1.1

Planned release date: ???

Planned new features and bug fixes:

JIRA Issues (9 issues)
Type	Key	Summary	Status
	BTM-73	Connection Pool monitoring and management	Closed
	BTM-94	Provide ability to eject connections on rollback failure	Closed
	BTM-97	Changes to make BTM friendlier for non-production environments	Closed
	BTM-99	NPE in JMS pool when enlisting session after creating it outside of global transaction context	Closed
	BTM-100	Add Jetty 7 lifecycle	Closed
	BTM-101	Resource pools which fail initialization b/c of incremental recovery cannot be reinitialized	Closed
	BTM-102	race condition in disk force batching causing deadlocks	Closed
	BTM-104	JMX registration of Recoverer fails when multiple serverIds are used	Closed
	BTM-105	SchedulerNaturalOrderIterator causes infinite loop	Closed

Released versions

Version 2.1.0

Release date: 31 October 2010

Planned new features and bug fixes:

JIRA Issues (4 issues)
Type	Key	Summary	Status
	BTM-88	Rollback makes LrcXAResource unusable	Closed
	BTM-89	BTM errors occur after using resource.ds.minPoolSize>0 and waiting for 10 hours	Closed
	BTM-91	Migrate build to maven 2	Closed
	BTM-93	Detect dead JMS connections with a javax.jms.ExceptionListener	Closed

Version 2.0.1

Release date: 31 July 2010

New features and bug fixes:

JIRA Issues (3 issues)
Type	Key	Summary	Status
	BTM-84	Cannot recover lost JMS Connection	Closed
	BTM-85	NullPointerException in BitronixTransactionSynchronizationRegistry	Closed
	BTM-86	deadlock in JMS connection pool	Closed

Version 2.0.0

Release date: 2 July 2010

Planned new features and bug fixes:

JIRA Issues (24 issues)
Type	Key	Summary	Status
	BTM-32	Extend connection pool manageability through JMX	Closed
	BTM-35	Support per connection transaction affinity	Closed
	BTM-56	BTM is not compatible with JDBC 4 API	Closed
	BTM-57	BTM incompatible with Spring's JmsTemplate due to too generic Exceptions	Closed
	BTM-58	Performance optimizations	Closed
	BTM-59	Bitronix evicting/closing an in-use PreparedStatement from cache, causing a downstream failure	Closed
	BTM-60	NullPointerException in XAPool.containsXAResourceHolderMatchingGtrid()	Closed
	BTM-61	BTM should close statements as soon as the user closes the connection	Closed
	BTM-62	Allow setting other connection defaults besides isolation level	Closed
	BTM-63	ACCESSIBLE connection closed due to Recoverer failure (nothing prevents recoverer from running twice in parallel)	Closed
	BTM-64	If an exception in BTM.begin() occurs, the transaction context is incorrect	Closed
	BTM-65	Add JTA 1.1 support	Closed
	BTM-66	Memory retention problem due JdbcPooledConnection uncachedStatements list	Closed
	BTM-67	Transaction interleaving support broken	Closed
	BTM-68	BitronixTransactionManager.resume() gradually slower when called very often	Closed
	BTM-69	Prepare LRCXaResource although one of other resource prepare have failed.	Closed
	BTM-70	Tomcat/Jetty lifecycle jars not in Maven repo	Closed
	BTM-71	DualSessionWrapper.createBrowser() does not perform automatic enlistment	Closed
	BTM-72	Add support for EHCache	Closed
	BTM-76	Multiple threads hang waiting on DiskForceWaitQueue	Closed
	BTM-79	BitronixTransaction swallows any runtime exception thrown during beforeCompletion	Closed
	BTM-80	Report transaction timeout as Warning	Closed
	BTM-81	detectJdbcVersion may lead to "java.lang.AbstractMethodError"	Closed
	BTM-82	Deploy source and javadoc to Maven Central along with build artifacts for releases and snapshots	Closed

Version 1.3.3

Release date: 25 October 2009

New features and fixed bugs:

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

Version 1.3.2

Release date: 17 October 2008

New features and fixed bugs:

JIRA Issues (1 issues)
Type	Key	Summary	Status
	BTM-31	Synchronization registering another Synchronization with a different position aborts transaction	Closed

Version 1.3.1

Release date: 28 September 2008

New features and fixed bugs:

JIRA Issues (7 issues)
Type	Key	Summary	Status
	BTM-23	Add the ability to set guarantee the isolation level of resource	Closed
	BTM-24	recovery engine does not fully supports clustering	Closed
	BTM-25	add shutdown support for app servers	Closed
	BTM-26	JMX must be disabled if a resource's uniqueName contains a ':' character	Closed
	BTM-28	Race condition when mixing global and local transactions	Closed
	BTM-29	Random CorruptedTransactionLogException thrown during swapJournalFiles under JDK 1.6	Closed
	BTM-30	Resource creation cannot map long primitives to vendor's XADataSource	Closed

Version 1.3

Release date: 18 August 2008

New features and fixed bugs:

JIRA Issues (16 issues)
Type	Key	Summary	Status
	BTM-4	Implement incremental recovery	Closed
	BTM-7	Resource password is not decrypted when using the API	Closed
	BTM-8	Durable subscribers cannot participate in XA	Closed
	BTM-9	BitronixTransactionManager JNDI reference throws NPE on toString()	Closed
	BTM-10	Race condition in connection pools when lazily initialized	Closed
	BTM-11	Implement an embedded JNDI provider that allows to retrieve the TM and configured resources in a more standard way	Closed
	BTM-12	add maven support	Closed
	BTM-13	Implement ordering of XAResource during 2PC execution	Closed
	BTM-14	Need the ability to have BTM invoke specific methods on JDBC connection upon return to the pool	Closed
	BTM-16	Transaction.commit() does not disassociate the tx from the thread	Closed
	BTM-17	Set tx status to marked_rollback on timeout	Closed
	BTM-18	Invoke XAResource.setTransactionTimeout() when a resource is enlisted	Closed
	BTM-19	No effect by setting auto-commit to false on LrcConnectionHandle	Closed
	BTM-20	XAResourceManager incorrectly checking resource joinability	Closed
	BTM-21	Differing journal-file lengths cause BTM to fail to start even if skipCorrectedLogs is true	Closed
	BTM-22	Resource rollback not handled properly	Closed

Version 1.2

Release date: 27 January 2008

New features and fixed bugs:

JIRA Issues (6 issues)
Type	Key	Summary	Status
	BTM-6	Support for JMS credentials	Closed
	BTM-3	Upgrade to latest version of SLF4J	Closed
	BTM-12	add maven support	Closed
	BTM-2	error not reported when XAResource.recover() call fails	Closed
	BTM-5	pooling of prepared statements / statement cache	Closed
	BTM-15	Handle MySQL XA semantics	Closed

Version 1.1

Release date: 5 October 2007

New features and fixed bugs:

• Made pooled objects unwrappable.
• Implemented dynamic pool size. Pools (both JDBC and JMS) can now grow and shrink.
• Implemented keepConnectionOpenUntilAfter2Pc in PoolingDataSource (required to support IBM DB2).
• Added resource password encryption capability.

Version 1.0.1

Release date: 6 September 2007

New features and fixed bugs:

JIRA Issues (1 issues)
Type	Key	Summary	Status
	BTM-1	error delisting resource error with Oracle 9	Closed

Version 1.0

Release date: 8 August 2007

New features and fixed bugs:

• Full JTA support.
• JMS and JDBC connection pools tested against and supporting a wide range of databases and JMS servers, both commercial and open-source.
• XA recovery support thanks to the embedded disk logger.
• Usable standalone, with Spring and embeddable into servlet contains such as Jetty and Tomcat.
• Ease of use, precise error reporting and few 3rd party dependencies.