Support Article
RDB-List error "Could not commit with auto-commit set on'
Summary
When trying to access a database table using an Obj-* or RDB-* rule, a log error is generated. The error occurs even when running a Report Definition, when accessing a page other than the first with results. The error message pops up on every access to the table.
Error Messages
Caused by: java.sql.SQLException: Could not commit with auto-commit set on
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:4443)
at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:4490)
at oracle.jdbc.driver.T4CConnection.doSetAutoCommit(T4CConnection.java:943)
at oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:4320)
at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.setAutoCommit(DatabaseConnectionImpl.java:794)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnectionFromDatabaseName(ConnectionManagerImpl.java:830)
... 124 more
Steps to Reproduce
Run a RDB-List rule multiple times in a row.
Root Cause
A defect or configuration issue in the operating environment. This is a bug in the Oracle JDBC driver, ojdbc7.jar version 12.1.0.1.0.
Resolution
Make the following change to the operating environment:
Upgrade to the ojdbc7.jar version 12.1.0.2.0 of the JDBC driver.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.