We’ve restricted access to http://repo.atomikos.com (our maven repository) to customers only, so they can have easy and timely access to bug fixes, maintenance releases and full feature releases.
If you’re not a customer then you have two options:
In the near future we plan to distribute TransactionsEssentials exclusively via the central maven repo.
We have released 3.8 of Atomikos ExtremeTransactions and TransactionsEssentials software. This release includes a number of new features including:
You can download the release from our website.
We’ve finally managed to publish our online training via Parleys - feel free to check it out!
From now on, everybody world-wide can purchase our training sessions and follow at them at a self-paced rhythm. Training when you want it, at your fingertips!
We’ve just released the 3.7.1 (bug fix) releases for ExtremeTransactions and TransactionsEssentials - enjoy!
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…
The 3.7.0M5 milestone releases are now online, available via our homepage!
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…
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!
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:
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.