-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot invoke a rollback operation when the AutoCommit mode is set to "true" in tomcat-8.5.14 #195
Comments
Hi, The 4.0 is pretty old. Any way you can try with the current 6.0? Guy |
Thank you for your quick response @GuyPardon We were using atomikos-integration-extension-3.7.2.jar for EnhancedTomcatAtomikosBeanFactory. It seems like atomikos-integration-extension-3.7.2.jar which is deprecated since Atomikos 4.0.0, is not compatible with Atomikos 6.0.0, and I could not find the latest version or any documentation. Upgraded JARs: atomikos-integration-extension-3.7.2.jar (issue with compatibility, deprecated since Atomikos 4.0.0) ERROR I am currently searching for a solution. If you have any insights, please share. |
Hi, That tomcat integration jar was not maintained by us so I am not sure. We do have certified integration modules in our commercial distribution for which you can get a free trial. I realise this might not be what you want, just mentioning. I am not sure if the old jar would work with 5.0 instead. Guy |
@GuyPardon We are interested in exploring the free trial option. Could you please provide us with more information on how to proceed? |
Hi All,
We are currently managing a Spring Hibernate web application operating on Tomcat 8.x, with Atomikos 4.0.4 serving as the transaction manager. The backend database is SQL Server.
We have encountered an issue during write operations under high loads, where the system occasionally throws an error stating, "Cannot invoke a rollback operation when the AutoCommit mode is set to 'true'." This occurrence is primarily observed when executing transactions with elevated workloads.
To provide additional context, our application utilizes a JNDI connection configured as follows:
Resource name="JDBC/test" auth="Container" type="com.atomikos.jdbc.nonxa.AtomikosNonXADataSourceBean" factory="com.atomikos.tomcat.EnhancedTomcatAtomikosBeanFactory" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver
The error trace associated with this issue is as follows:
Any assistance or guidance you could provide on resolving this issue would be greatly appreciated.
Thank you for your time and consideration.
Shiju
The text was updated successfully, but these errors were encountered: