[jira] Resolved: (RIVER-296) Mahalo implementation throws CannotAbortException from abort() on an expired transaction

["Jukka Zitting (JIRA)" <ji...@apache.org>]

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

Jukka Zitting resolved RIVER-296.
---------------------------------

       Resolution: Fixed
    Fix Version/s: AR3
         Assignee: Jukka Zitting

Patch committed in revision 738114. Thanks!

> Mahalo implementation throws CannotAbortException from abort() on an expired transaction
> ----------------------------------------------------------------------------------------
>
>                 Key: RIVER-296
>                 URL: https://issues.apache.org/jira/browse/RIVER-296
>             Project: River
>          Issue Type: Bug
>          Components: com_sun_jini_mahalo
>    Affects Versions: AR1
>            Reporter: Robert Resendes
>            Assignee: Jukka Zitting
>             Fix For: AR3
>
>         Attachments: RIVER-296.patch
>
>
> [Excerpts from javaspaces users thread: http://archives.java.sun.com/cgi-bin/wa?A2=ind0805&L=JAVASPACES-USERS&T=0&F=&S=&P=3061]
> =======================
> When using a transaction whose lease has expired:
> 1) Using in conjunction with space operations, you get an 
> UnknownTransactionException.
> 2) Aborting that transaction results in a CannotAbortException (which 
> has no cause included).
> 3) Committing that transaction results in an UnknownTransactionException.
> Why does the failed abort result in CannotAbort, but the failed commit 
> does not result in CannotCommit?   Why not throw UnknownTransaction in 
> every case?
> =======================
> > Why does the failed abort result in CannotAbort?
> Good question, looks like an implementation bug to me. (Feel free
> to file an Apache River JIRA bug.)  The spec seems clear that
> CannotAbortException should only be thrown if the transaction manager
> knows the transaction previously committed.

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