Exception is thrown by TransactionManager when multiple commits are issued
against a started transaction.
---------------------------------------------------------------------------------------------------------
Key: IBATIS-228
URL: http://issues.apache.org/jira/browse/IBATIS-228
Project: iBatis for Java
Type: Bug
Components: SQL Maps
Versions: 2.1.6
Reporter: Jeff Roberts
The following exception is thrown when issuing multiple commits against a
started transaction.
com.ibatis.common.jdbc.exception.NestedSQLException:
Could not commit transaction. Cause:
com.ibatis.sqlmap.engine.transaction.TransactionException:
TransactionManager could not commit. No transaction
is started.
The problem is that the TransactionManager is throwing this exception in all
cases except when the Transaction State is STATE_STARTED. In this scenario,
the transaction has been started, but its state is STATE_COMMITTED.
Clinton asked me to log this issue and attach my fix. The fix is in the
TransactionManager.commit method and allows a commit to be performed if the
Transaction state is either STATE_STARTED or STATE_COMMITTED.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
