Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 69 Next »

Roadmap

Unscheduled yet

  • Implement LogLess Transactions optimization, see: http://blogs.sun.com/fkieviet/entry/logless_transactions.
  • Implement a generic XAResourceHolder that calls public XAResource getXAResource() via reflection on some passed-in object. This should allow manual enlistment of any kind of resource, not just JDBC and JMS.
  • Implement JTA 1.1 (TransactionSynchronizationRegistry).
  • Implement XATerminator, this will allow BTM to support propagation of the transactional context to/from another JVM.
  • Add support for JCA.

Unreleased versions

Version 2.0.0

Planned release date: ???

Planned new features and bug fixes:

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

Version 1.3.4

Planned release date: ???

Planned new features and bug fixes:

Loading
Type Key Summary Status

Released versions

Version 1.3.3

Release date: 25 October 2009

New features and fixed bugs:

Loading

Version 1.3.2

Release date: 17 October 2008

New features and fixed bugs:

Loading

Version 1.3.1

Release date: 28 September 2008

New features and fixed bugs:

Loading

Version 1.3

Release date: 18 August 2008

New features and fixed bugs:

Loading

Version 1.2

Release date: 27 January 2008

New features and fixed bugs:

Loading

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:

Loading
Type Key Summary Status
Bug 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.
  • No labels