Why did my JDBC code throw a rollback SQLException?
A. Your JDBC code may throw the following exception:”The coordinator has rolled back the transaction. No further JDBC access is allowed within this transaction.” The WebLogic JTS JDBC driver throws this exception when the current JDBC connection transaction rolls back prior to or during the JDBC call. This exception indicates that the transaction in which the JDBC connection was participating was rolled back at some point prior to or during the JDBC call. The rollback may have happened in an earlier EJB invoke that was part of the transaction, or the rollback may have occurred because the transaction timed out. In either case, the transaction will be rolled back, the connection returned to the pool and the database resources released. In order to proceed, the JTS JDBC connection must be closed and reopened in a new transaction.
Related Questions
- Can I mix both JDO and JDBC code on the same transaction/connection? For example, I would like to make a JDO query to fetch objects but update database records using Open SQL/JDBC?
- I’ve encountered a JDBC exception in my code. What is the minimum information to provide to Ingres support or on the forum when this happens?
- Can I rollback configuration and code changes with Makara?
