You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Jeff Roberts (JIRA)" <ib...@incubator.apache.org> on 2005/12/01 20:33:30 UTC
[jira] Created: (IBATIS-228) Exception is thrown by TransactionManager when multiple commits are issued against a started transaction.
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
[jira] Closed: (IBATIS-228) Exception is thrown by TransactionManager when multiple commits are issued against a started transaction.
Posted by "Clinton Begin (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATIS-228?page=all ]
Clinton Begin closed IBATIS-228:
--------------------------------
Fix Version: 2.2.0
Resolution: Fixed
Assign To: Clinton Begin
As described.
> 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
> Assignee: Clinton Begin
> Fix For: 2.2.0
> Attachments: TransactionManager.java
>
> 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
[jira] Updated: (IBATIS-228) Exception is thrown by TransactionManager when multiple commits are issued against a started transaction.
Posted by "Jeff Roberts (JIRA)" <ib...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/IBATIS-228?page=all ]
Jeff Roberts updated IBATIS-228:
--------------------------------
Attachment: TransactionManager.java
Fix to a bug in TransactionManager that prevents multiple commits to be issued against a started transaction.
> 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
> Attachments: TransactionManager.java
>
> 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