I've been occasionally getting the following error message when queries execute despite the fact my connections are created explicitly with autoCommit set to false.
Any ideas how something like this could happen? I've checked to make sure that the connections aren't getting autoCommit set to true at any point as well.
com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Connection is currently in auto commit mode.
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345)
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:113)
at com.sap.db.jdbc.ConnectionSapDB.commit(ConnectionSapDB.java:332)
at com.sap.db.jdbc.trace.Connection.commit(Connection.java:155)
at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sap.core.persistence.jdbc.trace.TraceableBase$1.invoke(TraceableBase.java:44)
at com.sun.proxy.$Proxy18.commit(Unknown Source)
at com.sap.core.persistence.jdbc.trace.TraceableConnection.commit(TraceableConnection.java:214)
at org.apache.commons.dbcp.DelegatingConnection.commit(DelegatingConnection.java:334)
at org.apache.commons.dbcp.DelegatingConnection.commit(DelegatingConnection.java:334)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.commit(PoolingDataSource.java:211)
at com.vertexinc.veta.memcalc.core.dao.impl.RptFactDeleteTask.call(RptFactDeleteTask.java:103)
at com.vertexinc.veta.memcalc.core.dao.impl.RptFactDeleteTask.call(RptFactDeleteTask.java:25)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:812)