geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (GERONIMO-4438) TransactionSynchronizationRegistry.getTransactionKey should return null when transaction is not associated with the current thread
Date Wed, 03 Dec 2008 02:54:44 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lin Sun resolved GERONIMO-4438.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2

fixed in txmanager 2.2-snapshot and 2.1.1 branch (see subversion commit).   this behavior
is documented in page 45 of the jta 1.1 spec.

> TransactionSynchronizationRegistry.getTransactionKey should return null when transaction
is not associated with the current thread
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4438
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4438
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>            Reporter: Lin Sun
>            Assignee: Lin Sun
>            Priority: Minor
>             Fix For: 2.2
>
>
> per JTA 1.1 spec, the TransactionSynchronizationRegistry.getTransactionKey method should
return null, if a transaction is not associated with the current thread.   The Geronimo transaction
impl (v2.1.1) throws an IllegalStateException which is incorrect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message