[RIVER-65] When can a TransactionManager give up on a commit?

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: jtsk_2.1
• Component/s: com_sun_jini_mahalo
• Bugtraq ID: 4251161
• Assignee: Unassigned
• Reporter: Robert Resendes
• Created: 26/Jul/07 16:24
• Updated: 26/Jul/07 16:24

Description

Bugtraq 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.