You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ludovic Orban (JIRA)" <de...@geronimo.apache.org> on 2006/05/09 08:17:22 UTC
[jira] Commented: (GERONIMO-594) Begin on TransactionManager always
fails when thread is associated with a Tx
[ http://issues.apache.org/jira/browse/GERONIMO-594?page=comments#action_12378573 ]
Ludovic Orban commented on GERONIMO-594:
----------------------------------------
I disagree with your comment David.
In the JTA 1.0.1 spec, page 10 paragraph 3.2.2 'Completing a Transaction' one can read: 'After the commit method returns, the calling thread is not associated with a transaction'. The same also applies to rollback.
> Begin on TransactionManager always fails when thread is associated with a Tx
> ----------------------------------------------------------------------------
>
> Key: GERONIMO-594
> URL: http://issues.apache.org/jira/browse/GERONIMO-594
> Project: Geronimo
> Type: Bug
> Components: transaction manager
> Versions: 1.0-M3
> Reporter: Dain Sundstrom
> Assignee: David Jencks
>
> The TransactionManager.begin() always throws an exception it thread is already associated with a transaction. This means the following code will fail:
> txManager.getTransaction().commit();
> txManager.begin();
> Also, I'm not sure if transaction.commit() should remove any thread association with the transaction.
--
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