Archive for the ‘Releases’ Category

Releases 3.7.0 available

Saturday, February 26th, 2011

Good news: we’ve finally released our 3.7.0 release, with improved performance as the main focus. Although previous milestone builds have been released on repeated occasions, this is now the official 3.7.0 release for both TransactionsEssentials (open source, not supported) as well as ExtremeTransactions (not open source, subscription-based availability, with support).

To download, proceed to our homepage.

As per our new policies, the open source TransactionsEssentials product is now also available via maven central - including clean poms, sources that match the binaries and all other things that maven users deserve…

Maven staging repo for our 3.7.0M5 build

Tuesday, December 7th, 2010

Hi,

The Sonatype maven staging repo for our latest build is available here

Enjoy!

Releases 3.7.0M5 now ready!

Wednesday, November 24th, 2010

The 3.7.0M5 milestone releases are now online, available via our homepage!

Releases 3.7.0M4 ready

Friday, October 22nd, 2010

The next milestone build in our new maven ecosystem is ready!

We’ve fixed a lot of cosmetic issues from the previous releases (but expect no perfection yet:-).

Available on our website

Releases 3.7.0M2 are out!

Tuesday, October 12th, 2010

Big news: our new 3.7.0M2 releases are out for ExtremeTransactions and TransactionsEssentials!

If you look at the release notes then you will see that there are not that many new features (besides bug fixes and some important performance tuning). So what makes these new releases big news then? It’s our new release process and build infrastructure that made them possible.

That’s right: we have a new build process. We are now officially using maven and mercurial for our builds, instead of ant and svn. Also, we have tuned our repository architecture to better match our business model: we are now tuned towards more frequent releases of ExtremeTransactions and optimized even more for our support business.

So we hope you enjoy the new releases as much as we do! Beware though: they are milestone builds, meaning they are bound to have minor issues still. This is mostly due to initial imperfections in our new build process. After all, it _is_ a new way of working for all of us!

Reflections on the testQuery property

Monday, September 27th, 2010

The Atomikos connection pooling mechanism invalidates connections when there are any errors - just to be sure that later transactions are not corrupted by prior errors on the connection stream to the back-end. Also, sometimes connections simply time out in the back-end, and are closed without warning. So it may happen that you have some ‘erroneous’ connections in the pool at any given time, and you will only find out the next time you try to use one of these connections (i.e., in your application logic you will see exceptions related to this).

To avoid this (and have the pool proactively validate connections for you) just set a testQuery on the AtomikosDataSourceBean instance. The idea is that you supply a snippet of SQL code that can be used by the pool to test if the connection is still valid. If not, it will be replaced automatically - and you should never get any erroneous connection out of the pool.

The fact that the testQuery is optional has been confusing to some users. Consequently, we’ve been asked to make it required or default to something meaningful. We’ve seriously thought about this, but there are a few problems here:

  • Making it required means breaking a lot of existing, working configurations when they upgrade to our newest release. That is because these existing configurations usually do not include any testQuery settings and the new release would fail to read the configuration and initialize correctly - thereby breaking backwards compatibility. We did not want to do this.
  • Providing a reasonable default is equally difficult, if not even harder: it turns out that there is no known SQL statement that will work for all DBMS. So our default testQuery - whichever we choose - would always fail on some systems. We did not want to do this either.

So what did we do to improve this? After some input from our LinkedIn group we now have a serious warning message in the logs whenever you don’t set the testQuery.

Note: this will be available in our very next release - due beginning of October.

TransactionsEssentials 3.6.5 released

Tuesday, April 20th, 2010

Hi,

We’ve just released TransactionsEssentials 3.6.5 - available as usual via our download page or via the Maven repo.

Cheers

Quick Update: Maven

Thursday, April 8th, 2010

Our maven integration has not been the most fluent thing we ever did, but we now seem to have gained some traction in the right direction (thanks to community hints, some solid teamwork and hours of additional brain-storming). Here is a quick update on where we are:

  • Upload to maven central is working but not yet optimal (we’re working on that).
  • Meanwhile, we’re also re-evaluating our entire build environment to optimize for maven builds (i.e., switching from ant to maven entirely).
  • We’re also restructuring our SVN repository so it has optimal support for our business model.

As you can see, we’re not afraid to throw away anything in our quest to improve things :-) Contrary to what I expected, going from ant to maven seems to simplify our build after all: maven seems to be maturing, and new team members tend to know maven better than ant.

All these changes have quite some impact on the architecture of our build ecosystem, so we can’t just do them overnight. However, we would like to have them ready before we bring out the next major new release(s).

Thank you for your patience!

TransactionsEssentials 3.6.4 released

Thursday, April 8th, 2010

You can download here

TransactionsEssentials 3.6.3 released

Monday, March 15th, 2010

You can download here…