geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-594) Begin on TransactionManager always fails when thread is associated with a Tx
Date Tue, 09 May 2006 07:39:25 GMT
    [ ] 

David Jencks commented on GERONIMO-594:

The paragraph you refer to describes the behavior of TransactionManager.commit(), not Transaction.commit()
which was the subject of my comment.  There is no doubt whatsoever that TransactionManager.commit()
must remove any transaction-thread association.  This paragraph does not specify anything
about the behavior of Transaction.commit().  

In section 3.3.3, Transaction.commit() is described briefly, and it's noted that the calling
thread may have a different transaction association than the transaction it is calling commit
on.  This implies that transaction.commit() cannot have any affect on the transaction-threads
associations the transaction may be participating in.

The jta spec is notoriously bad and incomplete.  More reasonable sources for information about
xa are the x-open xa spec and the corba transaction spec, although the latter has quite a
few non-xa features.

> Begin on TransactionManager always fails when thread is associated with a Tx
> ----------------------------------------------------------------------------
>          Key: GERONIMO-594
>          URL:
>      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:
For more information on JIRA, see:

View raw message