river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Resendes (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-65) When can a TransactionManager give up on a commit?
Date Thu, 26 Jul 2007 16:26:04 GMT
When can a TransactionManager give up on a commit?

                 Key: RIVER-65
                 URL: https://issues.apache.org/jira/browse/RIVER-65
             Project: River
          Issue Type: Improvement
          Components: com_sun_jini_mahalo
    Affects Versions: jtsk_2.1
            Reporter: Robert Resendes
            Priority: Minor

Bugtraq ID [4251161|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4251161]

According to TX.2.7 a TransactionManager can only giveup on notifing a particpate of a commited
transaction if it gets back UnkownTransactionException or NoSuchObjectException.  Might also
think giving up would be acceptable after
various Errors and RuntimeExceptions.

In a related mater the language in TX.2.6 does not make it clear that a particpate can drop
out of a transaction it has prepared if it gets a NoSuchObjectExcpetion or a UnkownTransactionException
(again what about Errors and RuntimeExceptions?)

Should add "definite exception" language to the discussion of when a manager/participant can
release resources.

Participant language should be added for abandoning the prepared case as well.
For example, participant1 votes PREPARED, but participant2 votes to ABORT and
the manager gives up notifying participant1 to abort. When participant1 queries
the manager with getState() and it receives an UnknownTransaction, it should be
able to release it's "prepared" state.

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

View raw message