The TransactionControl interface has been removed from our API and its remaining functionality has been merged into the CompositeTransaction interface.
The Map is cleaner at API level (not a JDK implementation class).
Added a contributed improvement for dynamically registered XAResource instances so we avoid race conditions under high load.
We now avoid serialisation with our brand-new recovery implementation.
OLTP logging and restart/crash recovery logic are now separated, which simplifies the transaction state handlers and puts us on the road to improved compatibility with cloud deployments.
Shutdown used to be binary: either you waited for active transactions to finish, or not. We've now added an option of specifying a timeout in milliseconds. The system will wait for active transactions to finish within the specified delay, and resort to forced shutdown after that.
For now, this module is no longer compatible with the new logging/recovery and has been removed. Later on, we'll consider the equivalent for the new logging mechanism.
We changed this in an attempt to make resource names more unique. A more profound solution will be available in a later release, when we improve dynamic resource registration.http://fogbugz.atomikos.com/default.asp?community.6.3133.0
This feature is no longer needed in our modernised code base so we have removed it.
The build now works on/with the latest JDK versions.
All built-in primitive types are now supported.
We've added one big zip file for all demos - this is simpler to handle for everybody.
The license checks have been removed to alleviate administrative overhead for everybody.
The OSGi examples are now included again. Previously, they were excluded because the build used to fail on them.
Our coordinator service implementation did not properly set the Accept header when confirming a participant service. This has been fixed.
The following methods are sure to be allowed after close: rollback, setRollbackOnly, suspend, resume.
Documented the event mechanism (in the PDF guide covering the API).
It is now possible to quickly launch a coordinator server from the TCC demos so you can easily test your own participant services for compliance.ExtremeTransactions 3.9.3 for details.
Added runnable example to demonstrate Hibernate 4 integration.
The log level has been increased to avoid losing time chasing errors that happen during beforeCompletion and prevent committing the transaction.
We now support hibernate 4 in an easy way, as demonstrated by the corresponding new examples.
We now avoid writing .epoch files for increased flexibility and usability.
We've replaced our existing web services and SOA support by the long-awaited TCC for REST support. This was implemented as a plugin module around the core.
JMX support is now divided across 2 modules; one transactions-jmx (core) module and also transactions-jmx-jta for specifics relevant to JTA.ServiceLoader mechanism).
The TSListener interface has been refactored and renamed to be the main plugin interface for our new core architecture.forum post):
In order to activate JTA or RMI functionality, it now suffices to put these modules (jars) in the classpath and they will be discovered automatically during startup of the core. Other modules (like REST support) will later be added in the same way.
This functionality seemed a bit exotic to carry on in our codebase, so we've optimistically removed it for now. Should there be compelling use cases to add them again, we will do so at a later time. Most of our user base adheres to the JTA/JDBC/JMS API and will not be affected at all by this removal.
Added a new constructor that accepts the ConfigProperties as parameter. This allows reuse of config parameters that are looked up by the core startup.
This has now been fixed.
We no longer need Swing libraries: these have long been replaced by JMX support.
Disabling transaction logging now works again.
This setting got ignored in the 3.9 release, meaning there was no way to turn logging off - this has now been fixed.
The evaluation download contained old release notes - these have been removed. Release notes are now online only.