The Atomikos Blog

Archive_web

You are here: Blog

Synchronous microservices look great on paper.

They are easy to read, easy to debug, and they map perfectly to how we think: “I send a request, I get a reply.” No surprises, right?

Except when things go wrong. Which in distributed systems is most of the time.

ExtremeTransactions 6.0.114
Release notes for 6.0.114

08 April 2025 | Guy Pardon | Release notes

Feature211440
Improve micrometer metrics support for the pool usage: add getPercentageOfPoolCapacityUsed

You can now see the pool's percentage used (wrt its capacity) in our Micrometer support module.

Technical details

The ability to see the pool's percentage used (wrt its capacity) was already present in our JMX module, but not in our Micrometer support. This has now been added.

Changes impacting client API

None.

Bug214569
Fix pom dependency for Spring Boot 3.4 starter

Severity:4
Affected version(s):6.0.113

Description

You can now use the new Spring Boot 3.4 starter.

Technical details

The module transactions-spring-boot3.4-starter had a dependency on com.atomikos.transactions-spring-boot3, whereas it should have had a dependency on com.atomikos.transactions-spring-boot3.4. This has been fixed.

Changes impacting client API

None.

Bug212902
Improve error message on enlist / timeout

Severity:3
Affected version(s):6.0.x

Description

The error message on potential timeouts is now better.

Technical details

Some cases would report an error like "The transaction has timed out - try increasing the timeout if needed" when in fact the cause was a wrong state of the transaction.

This has been improved to also show state information:

"The transaction has potentially timed out (state: " + state + ") - try increasing the timeout if needed"

Changes impacting client API

None.

Bug212919
Improve thread-safety of CheckedExportingTransactionManager

Severity:2
Affected version(s):6.0.x

Description

The implementation of this class is now safer for multi-threaded use.

Technical details

The attribute pendingRequestSynchronisation used to be a HashMap and is now a ConcurrentHashMap.

Changes impacting client API

None.

Bug212877
Tomcat examples: fix port number in the README

Severity:4
Affected version(s):6.0.x

Description

The port number has been corrected in the README of the tomcat examples.

Technical details

The README file would contain port 8080 instead of 8888. This has been fixed.

Changes impacting client API

None.

Bug212878
Update tomcat examples to make docker include the latest release

Severity:4
Affected version(s):6.0.x

Description

The new Tomcat examples should now include the right Atomikos release.

Technical details

Due to an issue with maven plugins, the examples would not always ship the right Atomikos release. This has now been fixed.

Changes impacting client API

None.

Issue214480
Disable OSGi examples build

Severity:4
Affected version(s):6.0.x

Description

The OSGi examples are now skipped during the build.

Technical details

The OSGi examples used bundle dependencies hosted on a Spring repository site that has been discontinued. This made the build fail. Until we find a solution, we had to disable this module during the build (or releases would be blocked).

Issue215322
Zip files with example projects not uploaded correctly

Severity:4
Affected version(s):6.0.x

Description

The zip files with example projects failed to upload.

Technical details

When trying to download the example projects from the installation page(s) you will get "404 Not Found" errors. We are looking into it but decided not to let this block a maintenance release like this one.

ExtremeTransactions 6.0.113
Release notes for 6.0.113

27 February 2025 | Guy Pardon | Release notes

Feature211078
Add Spring Boot 3.4 starter

You can now use Atomikos with Spring Boot 3.4.

Technical details

Spring Boot 3.4 required a new starter project to make it work with Atomikos.

Attempting to use Spring Boot 3.4 with the older starter project would result in errors like this:

Caused by: java.lang.NoSuchMethodError: 'void org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers.customize(org.springframework.transaction.PlatformTransactionManager)'
  at com.atomikos.spring.AtomikosAutoConfiguration.lambda$transactionManager$0(AtomikosAutoConfiguration.java:84)
  at org.springframework.beans.factory.support.DefaultListableBeanFactory$DependencyObjectProvider.ifAvailable(DefaultListableBeanFactory.java:2382)
  at com.atomikos.spring.AtomikosAutoConfiguration.transactionManager(AtomikosAutoConfiguration.java:84)
  at java.base/java.lang.reflect.Method.invoke(Method.java:580)
  at org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171)
  ... 50 more

This was due to Spring's removal of some deprecated methods in org.springframework.boot.autoconfigure.transaction.TransactionManagerCustomizers. A new starter project was needed to fix this.

Changes impacting client API

You can now just use the new starter for your project.

Feature208173
Improve error message when JDBC driver does not return a valid connection

You now get a meaningful error message when the JDBC driver does not return a valid connection.

Technical details

When the JDBC driver does not return a valid connection, this would result in a cryptic exception like this:

java.lang.NullPointerException: Cannot invoke "Object.getClass()" because "this.delegate" is null
                at com.atomikos.util.DynamicProxySupport.getClassLoadersToTry(DynamicProxySupport.java:195) ~[atomikos-util-6.0.112.jar:na]
                at com.atomikos.util.DynamicProxySupport.createDynamicProxy(DynamicProxySupport.java:189) ~[atomikos-util-6.0.112.jar:na]
                at com.atomikos.jdbc.internal.AtomikosNonXAPooledConnection.doCreateConnectionProxy(AtomikosNonXAPooledConnection.java:108) ~[transactions-jdbc-6.0.112.jar:na]
                at com.atomikos.jdbc.internal.AtomikosNonXAPooledConnection.doCreateConnectionProxy(AtomikosNonXAPooledConnection.java:35) ~[transactions-jdbc-6.0.112.jar:na]
                at com.atomikos.datasource.pool.AbstractXPooledConnection.createConnectionProxy(AbstractXPooledConnection.java:101) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.datasource.pool.ConnectionPoolWithConcurrentValidation.concurrentlyTryToUse(ConnectionPoolWithConcurrentValidation.java:61) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.datasource.pool.ConnectionPoolWithConcurrentValidation.retrieveFirstAvailableConnection(ConnectionPoolWithConcurrentValidation.java:43) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.datasource.pool.ConnectionPool.retrieveFirstAvailableConnectionAndGrowPoolIfNecessary(ConnectionPool.java:140) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.datasource.pool.ConnectionPool.findOrWaitForAnAvailableConnection(ConnectionPool.java:128) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.datasource.pool.ConnectionPool.borrowConnection(ConnectionPool.java:119) ~[transactions-jta-6.0.112.jar:na]
                at com.atomikos.jdbc.internal.AbstractDataSourceBean.getConnection(AbstractDataSourceBean.java:375) ~[transactions-jdbc-6.0.112.jar:na]
                at com.atomikos.jdbc.AtomikosNonXADataSourceBean.getConnection(AtomikosNonXADataSourceBean.java:208) ~[transactions-jdbc-6.0.112.jar:na]

This has now been fixed: we now report that the "Driver didn't return a valid Connection".

Changes impacting client API

None.

Feature207950
Avoid unnecessary XA connection refresh on shutdown

We now avoid useless XA connection refreshing on shutdown.

Technical details

The following would happen upon shutdown, when for instance the JMS server was gone:

Failed to refresh XAResource
com.atomikos.datasource.ResourceException: Error in getting XA resource
        at com.atomikos.datasource.xa.jms.JmsTransactionalResource.refreshXAConnection(JmsTransactionalResource.java:83) ~[!/:?]
        at com.atomikos.datasource.xa.XATransactionalResource.refreshXAResource(XATransactionalResource.java:413) ~[!/:?]
        at com.atomikos.datasource.xa.XATransactionalResource.getXAResource(XATransactionalResource.java:227) ~[!/:?]
        at com.atomikos.datasource.xa.XATransactionalResource.isSameRM(XATransactionalResource.java:317) ~[!/:?]
        at com.atomikos.datasource.xa.XATransactionalResource.equals(XATransactionalResource.java:430) ~[!/:?]
        at java.util.Vector.indexOf(Vector.java:413) ~[?:1.8.0_381]
        at java.util.Vector.indexOf(Vector.java:387) ~[?:1.8.0_381]
        at java.util.Vector.removeElement(Vector.java:646) ~[?:1.8.0_381]
        at java.util.Vector.remove(Vector.java:804) ~[?:1.8.0_381]
        at com.atomikos.icatch.config.Configuration.removeResource(Configuration.java:263) ~[!/:?]
        at com.atomikos.jms.AtomikosConnectionFactoryBean.close(AtomikosConnectionFactoryBean.java:597) ~[!/:?]

This has been improved / fixed - we now avoid such refresh.

Changes impacting client API

None.

Bug208965
Connection pool: make waiting for connections fair(er)

Severity:4
Affected version(s):6.0.112

Description

Your getConnection requests now get the (new) connections they deserve.

Technical details

In our 6.0 release the connection pool grows via a separate background thread. When getConnection finds no available connection, it will start waiting for this thread to grow the pool and add a new connection to it.

The implementation was "unfair" in that a waiting getConnection request could (and would) see its new connection "hijacked" by a different, later getConnection request.

This has now been fixed.

Changes impacting client API

None.

Bug211208
Tomcat JNDI factory for JDBC and JMS: make it tolerate double lookups

Severity:4
Affected version(s):6.0.x, 5.0.x

Description

You can now safely repeat JNDI lookups for our JDBC and JMS factories bound in Tomcat's JNDI space.

Technical details

There was a race condition in our code that could lead to repeated initialisation of JNDI resources with the same name, like JDBC datasources or JMS connection factories.

This has now been fixed.

Changes impacting client API

None.

ExtremeTransactions 5.0.109
ExtremeTransactions 5.0.109 release notes

10 October 2024 | Guy Pardon | Release notes

Feature200360
Subscription files are now required for production use

Description

We now require customers to install subscription files for production use, similar to what we do in 6.0.

Technical details

We've had some bad experiences with subscriptions purchased via resellers / intermediaries, that were first used by a development team, then moved onto other teams in production without us being able to keep track. This has lead to unpleasant experiences for both our customers and ourselves.

For more details, see this documentation page.

Changes impacting client API

You need to install 2 files as explained on the documentation page mentioned above. Note: development or testing use does not need subscription files.

Feature201309
Detect vulnerable dependencies on classpath

Description

We now help you find out about known vulnerable maven dependencies that your application is using.

Technical details

With current hacker efforts moving more and more into the application stack via vulnerable open source dependencies, we notice customers are getting worried (or facing audits of their applications). Log4j, anyone?

Our approach has been two-fold:

  • We avoid 3rd party dependencies so you can't pull them in by accident, and
  • We now also detect known vulnerable 3rd party maven dependencies on your application's classpath

Starting in the near future, expect more and more "security updates" in that respect.

Changes impacting client API

None.

Bug197240
Allow spring.jta properties in Spring Boot starter

Severity:4
Affected version(s):5.0.x

Description

Any spring.jta properties in Spring Boot should now be taken into account.

Technical details

After the Spring Boot team contributed the source code for their Atomikos starter we thought it was safer to ignore any properties with the "legacy" prefix spring.jta.atomikos.properties (in your application.properties file for Spring Boot).

This has proven to confuse users, so we now take such spring.jta properties into account.

Changes impacting client API

Any spring.jta properties in Spring Boot should now be taken into account.

Bug197505
Avoid that defaults in the Spring Boot starter override jta.properties

Severity:4
Affected version(s):5.0.x

Description

You can now count on the property values from jta.properties to be taken into account even with Spring Boot.

Technical details

The Atomikos JTA properties implementation in our Spring Boot starter would define default values for many properties, meaning that their value specified jta.properties would not be taken into account. This has now been fixed.

Changes impacting client API

Your properties specified in jta.properties should now work.

Bug197362
Clarify message if rest port not set in client

Severity:1/2/3/4
Affected version(s):5.0.x

Description

You can now count on a better error message when the AtomikosRestPort URL is not set (for transactions across remoting calls).

Technical details

When the AtomikosRestPort URL was not set, the client template would report a misleading message saying that there is no transaction for the thread. Instead, the root cause is a URL that is missing - so we fixed that for you.

Changes impacting client API

None.

Bug197506
Support diamond case architectures for readOnly remoting

Severity:4
Affected version(s):5.0.x

Description

You can now use transitive readOnly remoting transactions in all cases.

Technical details

As outlined in this GitHub issue there was a problem with readOnly invocations when:

  • the same shared service was called over different paths, and
  • all invocations were readOnly

This is known as a "diamond case" because the invocation diagram looks like a diamond.

This issue has been fixed in the following way: our product will now avoid the readOnly optimisation in this specific scenario. This is still correct, at a minor performance overhead in the exotic cases where this does happen.

Changes impacting client API

None.

Bug197253
Suspend/resume should not change local sibling count

Severity:2
Affected version(s):5.0.x

Description

You can now use @RequiresNew with imported transactions.

Technical details

As explained in this GitHub issue, there were problems when a remote transaction was imported and then subsequently called local logic that was marked with @RequiresNew. As required by the specification of @RequiresNew, this would suspend any active transaction - and resume it later.

Our code had a side effect of suspend/resume that changed the local sibling count.

Sibling counts help detect orphaned invocations (and their transactional updates to persistent storage) that arise out of lost replies. For instance, consider this scenario with services A and B:

  1. A starts a transaction.
  2. A calls B as part of that transaction.
  3. B does work and returns a result.
  4. A does not receive the result due to a network timeout (so B now has an orphaned invocation).
  5. A tries again, so B performs the changes again and returns a new result (in the same transaction).
  6. A commits the transaction thinking it only updated B once.
  7. B commits the same transaction with two sets of updates.

This risk here is the different views of A and B regarding the scope of the transaction: A thinks it commits one update to B, whereas B commits two different updates. This can be a problem for data consistency, so we avoid this by keeping sibling counts at B and A. A constructs its sibling count picture with each result it actually receives with its replies from A. Before commit, A passes on the "count" it has for invocations at B, and if B finds that there is no match then it refuses to commit.

This would avoid the problem outlined above, because in step 4 service A will miss a count, so in step 6 service A will pass a count of 1 for service B, whereas B will see 2 and refuses the commit process.

In short, sibling counts have their purpose. However due to a bug, this was affected by a suspend/resume at service B (when it has @RequiresNew logic inside).

Changes impacting client API

You should now be able to configure @RequiresNew on any service that needs it.

Bug211208
Avoid init-ing connection factory twice or more on Tomcat JNDI lookups

Severity:4
Affected version(s):5.0.x

Description

You should now be able to perform any number of JNDI lookups in Tomcat without getting warnings about the resource already existing with the same name.

Technical details

During JNDI lookups, Tomcat applications would sometimes get warnings like below due to a race condition. This has been fixed.

WARNING: Cannot initialize AtomikosConnectionFactoryBean
java.lang.IllegalStateException: Another resource already exists with name XAConnectionFactory - pick a different name
      at com.atomikos.icatch.config.Configuration.addResource(Configuration.java:241)
      at com.atomikos.jms.AtomikosConnectionFactoryBean.doInit(AtomikosConnectionFactoryBean.java:440)
      at com.atomikos.jms.AtomikosConnectionFactoryBean.init(AtomikosConnectionFactoryBean.java:354)
      at com.atomikos.jms.AtomikosConnectionFactoryBean.createConnection(AtomikosConnectionFactoryBean.java:620)

Changes impacting client API

None.

ExtremeTransactions 6.0.110
Release notes for 6.0.110

02 October 2024 | Guy Pardon | Release notes

Feature207056
Improved core classes for concurrency / threading

You can now benefit from reduced synchronisation overhead thanks to concurrent maps usage in our core classes.

Technical details

We've added 2 new implementation classes: DefaultTransactionService and DefaultCompositeTransactionManager. These comply with our newly documented Concurrency Model for correctness in multi-threaded applications. We now also use concurrent maps thanks to this this contribution on github.

The new DefaultTransactionService also has better / simpler shutdown logic for the transaction service.

Changes impacting client API

This feature can (for now) be toggled with a flag in jta.properties:

   om.atomikos.icatch.feature.207056 = true 

This is enabled by default because we are confident it works better than before. If you experience problems after upgrading, set this to false...

Feature203242
Retry file lock on startup

You can now shift Kubernetes pods by starting a new pod while the old one is still terminating.

Technical details

In Kubernetes environments pods might be terminated and shifted to other nodes. Because of this the configured log path might be in use if the old pod is about to terminate and the new one is starting up. To be able to use the same LogFileLock we now offer retry attempts for the new pod which is trying to acquire the lock.

Changes impacting client API

None, we have reasonable default configuration properties in JTA Properties, prefixed with com.atomikos.icatch.log_lock_acquisition.

Feature201646
Spring Boot 2 starter: use the jta and jms versions of Spring Boot's POM in the starter project

You can now use the same JTA and JMS dependency versions of Spring Boot's rather than the ones we specify.

Technical details

For Spring Boot 2 we used to specify a particular version for each of JTA and JMS. This would override the versions that Spring Boot prefers. We no longer do this.

Changes impacting client API

None.

Feature207758
Examples for Hibernate 7

You can now check the examples for Hibernate 7.

Technical details

We've added working samples for Hibernate 7.

Bug202474
Refine exception message when creating a JDBC statement fails

Severity:3
Affected version(s):6.O.x, 5.0.x

Description

You can now expect more accurate exception messages when creating a JDBC statement fails

Technical details

We used to have one generic exception message when a statement could not be created, each time suggesting a timeout of the transaction. This was confusing if the real reason was, for instance, the transaction having been marked for rollback only.

The code has been refined live this:

   TxState state = ct.getState();
   if (state == TxState.ACTIVE) {
      ct.registerSynchronization(new JdbcRequeueSynchronization(this, ct));
   } else if (state == TxState.MARKED_ABORT){
      AtomikosSQLException.throwAtomikosSQLException("The transaction has been set to rollback-only");
   } else {
      AtomikosSQLException.throwAtomikosSQLException("The transaction has timed out - try increasing the timeout if needed");
   }

Changes impacting client API

None.

Bug202466
Interposed synchronisation instances not called on regular rollback

Severity:3
Affected version(s):6.O.x

Description

Interposed synchronisation instances are now called on regular rollback also.

Technical details

See this github issue for details.

Changes impacting client API

None.

Bug208965
Bug in borrowing connection: make waiting for available connections fair(er)

Severity:3
Affected version(s):6.0.x

Description

Getting a new connection is now more efficient.

Technical details

Details are explained in this github issue.

Changes impacting client API

None.

Bug209260
Expose AtomikosSQLException in public package (for OSGi)

Severity:4
Affected version(s):5.O.x, 6.0.x

Description

The class AtomikosSQLException was not exposed as public in OSGi.

Technical details

The class AtomikosSQLException was not exposed as public in OSGi because it was in an "internal" package. This class has been moved to a public package instead, so it can be used with OSGi.

Changes impacting client API

You have to change the imports when your code references this exception.

Bug207055
Bug in timeout/rollback of local sub transaction followed by commit of its parent

Severity:3
Affected version(s):5.0.x, 6.0.x and prior (decorated) releases

Description

Timeout / rollback of a subtransaction no longer appears as a commit to the parent transaction.

Technical details

Timeout with subsequent rollback of a subtransaction would interfere with a later commit of the parent transaction: the state handler for the subtransaction would erroneously reply with READONLY upon 2PC prepare. This would make it seem to the parent transaction as though commit may proceed. We've fixed this by checking for timeout upon prepare of a subtransaction. Most people are not using subtransaction functionality, but those who do will benefit from this fix.

Changes impacting client API

None.

Bug207046
Improve 2-phase commit for imported transaction to align with the new concurrency model

Severity:3
Affected version(s):5.0.x, 6.0.x and prior (decorated) releases

Description

We improved the way imported transactions are handled in the case of network timeouts - so it aligns with our concurrency model.

Technical details

This release includes an improved concurrency implementation (as per feature 207056 above), along with a newly documented concurrency model as shown in Concurrency Model. We've updated the handling of imported transactions to be consistent with the new concurrency model. In particular, the following scenario has been improved:

  • A remote client propagates a transaction to your service, possibly on a number of times on different invocations.
  • The last invocation "I" appears to "fail" at the remote client due to a network timeout, but the invocation as actually still active at your service.
  • The remote client decides to terminate the transaction by either commit (which is possible if "I" is considered optional) or rollback.
  • Depending on the complexity of the remote transaction, this will lead to either of an incoming "PC": prepare, rollback or 1-phase commit call in your service.
  • The classical way we dealt with this was instant rollback triggered by the incoming "2PC", but this violates our new concurrency model.
  • So we now let the pending active invocation do the rollback instead - in line with the concurrency model.

Changes impacting client API

None.

Bug207146
High memory consumption due to adding JDBC statements multiple times to the same list

Severity:3
Affected version(s):6.0.x

Description

Creating many JDBC statements no longer leads to high memory consumption.

Technical details

For technical reasons we keep a "cached" collection of JDBC statements. Due to a bug, such statements were added multiple times to a list. We fixed this by:

  • Changing the list to a Set, and
  • Removing the lines of code that added statements more than once.

Changes impacting client API

None.

Bug209259
Improve thread-safety of CheckedExportingTransactionManager

Severity:3
Affected version(s):5.0.x, 6.0.x

Description

We improved the tread-safety of CheckedExportingTransactionManager in module transactions-remoting.

Technical details

We changed the use of a HashMap to a ConcurrentHashMap for pending request synchronisation instances.

Changes impacting client API

None.

Bug202750
ConnectionPool: endless loop on interrupt during waitForConnection

Severity:3
Affected version(s):4.0.x, 5.0.x, 6.0.x

Description

Interruptions during Spring Boot shutdown are now handled better by the connection pool.

Technical details

Full details as disclosed in the original report:

We experienced a somewhat strange behaviour with Atomikos in a situation, where our application (Spring Boot) is shutting down while some threads are waiting for a connection. In this shutdown-situation, Spring Boot sends an 'interupt' to all running threads. The Atomikos ConnectionPool method 'waitForAtLeastOneAvailableConnection()' handles this InterruptedException by invoking the InteruptedExceptionHelper. This in turn logs the exception and re-interrupts the thread. This is the correct pattern to interrupt possible further waits in the call stack.

But the method does not leave the while-loop. This causes a loop for the remaining borrowConnectionTimeout, leading to a very large amount of exception logs.

Changes impacting client API

None.

Bug210111
Missing jar in eval download: transactions-tomcat-jakarta

Severity:4
Affected version(s):6.0.x

Description

You can now use the Tomcat Jakarta functionality in the free trial download.

Technical details

The relevant jar file for this was missing from the evaluation zip file. It has now been added.

Issue202334
Modify Tomcat examples to use Docker

Severity:4
Affected version(s):6.0.110

Description

The Tomcat examples have been modified to user Docker, but this does not work on all platforms yet.

Technical details

The Docker image generated to run the Tomcat examples contains a Java JDK that is not binary compatible with all platforms yet.

Corporate Information

Atomikos Corporate Headquarters
Hoveniersstraat, 39/1, 2800
Mechelen, Belgium

Contact Us

Copyright 2026 Atomikos BVBA | Our Privacy Policy
By using this site you agree to our cookies. More info. That's Fine