You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jim Waldo (JIRA)" <ji...@apache.org> on 2007/07/26 16:10:40 UTC
[jira] Created: (RIVER-50) Mahalo exception/retry logic should be
revisited
Mahalo exception/retry logic should be revisited
------------------------------------------------
Key: RIVER-50
URL: https://issues.apache.org/jira/browse/RIVER-50
Project: River
Issue Type: Improvement
Components: com_sun_jini_mahalo
Affects Versions: jtsk_2.1
Environment: All
Reporter: Jim Waldo
Priority: Minor
Mahalo's exception handling for TransactionParticipant calls mirrors that of ThrowableConstants. This is probably not a suitable categorization for Mahalo's purposes. For example, NoRouteToHostException, while unlikely to be resolved shortly (or by itself) would be "definite" exception according the ThrowableConstants. Mahalo, on the other hand, has a higher level of responsibility and should probably retry commit() calls, for example, even in the face of "unlike to be resolved" exceptions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.