It is now possible to use Hazelcast distributed caching as part of your transactions. If there is a rollback then any changes in the cache will rollback too. This is useful if you want to keep your cache consistent with your messaging and/or database, and it reduces the need for manual evicting from the cache.
This functionality has been tested against Hazelcast 3.5, which also includes XA support. Nevertheless, for recovery purposes you still need Atomikos functionality, covered in this release.
Some primitive types were as yet unsupported, like long / byte / floating point / char. Support for these has now been added.
Under certain circumstances, closing a connection twice could affect intermediate reuse from the pool. This has now been fixed.
Non-XA participants could not be deserialised from the logs without this extra dependency.
Our write-ahead module contained an obsolete license check that prevented it from working with recent customers who no longer have/need license files in their installation.
Our log utility now also shows statistics on the average byte size of log entries.
The configuration details to allow JMX-level changes of the log level have been added to the spring JMX example and to the wiki documentation.
The LogUtil application now also shows any heuristic messages.
When warnings are not appropriate, commit-level are logged is INFO anyway - to allow diagnosing the details by our support team.
Exceptions are now treated without warnings when possible - as in case 135274 and case 135291 and case 135290.
We now log a warning only if the maxPoolSize equals the default (rather than the minPoolSize).