Closed AhamBrahmasmi2020 closed 9 months ago
Hi,
This probably comes from the changes we made in 5.0, see the release notes for how to achieve backwards compatible behaviour with 3.9 and 4.0 applications:
https://www.atomikos.com/Blog/ExtremeTransactions5dot0
Cheers
Thanks for the quick reply.
My pleasure.
Issue:
After upgrading Atomikos version from 4.0.4 to 6.0.0, we are encountering two warnings:
Warning 1:
com.atomikos.logging.JULLogger.logWarning A JTA transaction is required but none was found - please start one first (or set localTransactionMode=true to allow JDBC transactions)
Warning 2:
WARNING [TestScheduler_Worker-2] com.atomikos.logging.JULLogger.logWarning com.atomikos.jdbc.AtomikosNonXADataSourceBean 'jdbc/MatriDBDataSource' [NB: this resource does not support two-phase commit unless configured as readOnly] WARNING [TestScheduler_Worker-2] com.atomikos.logging.JULLogger.logWarning This method needs a transaction for the calling thread and none exists. Possible causes: either you didn't start a transaction, it rolledback due to timeout, or it was committed already. ACTIONS: You can try one of the following:
Make sure you started a transaction for the thread. Make sure you didn't terminate it yet. Increase the transaction timeout to avoid automatic rollback of long transactions; Environment:
Spring Hibernate application NonXA transaction Are these warnings expected behavior after upgrading to Atomikos 6.0.0 ? If so, how can we address them?
Steps to reproduce:
Upgrade Atomikos from 4.0.4 to 6.0.0 Run the application Expected behavior:
No warnings should be generated.
Actual behavior:
The two warnings described above are generated.
We are concerned about these warnings and would appreciate any guidance on how to address them.