Not for product support. If you need urgent help with your project then buy development or production support or check the known problems...
One of the features in our backlog is: optimizing for 1-phase commit (i.e., when only one resource is involved in the transaction).
However, the killer use case for Atomikos is precisely when 2 or more resources are needed. Consequently, we've always been reluctant to changing the design of our core algorithms to fully support 1-phase commit in all possible cases.
The question to you: what do you think? Should we invest in redesigning our core to go for 1-phase commit even when we think this is marginal?
It would only benefit in the following case:
-only one resource (DataSource/ConnectionFactory) is used in the transaction, AND
-at least one Synchronization is registered
In practice, this translates into:
-Using JTA with Hibernate and only having JDBC (no JMS) to one database.
This topic is archived. No further replies will be accepted.Other recent topics