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-64) Ensure service changes are persisted prior to modifying active service state
Date Thu, 26 Jul 2007 16:24:04 GMT
Ensure service changes are persisted prior to modifying active service state
----------------------------------------------------------------------------

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


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

Mercury currently modifies active state then persists, in persistent modes, the changes to
disk. There are cases where persistence exceptions are swallowed. At best, this can cause
Mercury to be in an inconsistent state upon restart. At worst, this can cause Mercury to violate
the spec because supposedly "persistent" state doesn't survive a service restart.
 
Severity on this bug is low because it's unlikely to occur under expected/normal conditions.
Persisting log records should only fail if can't write to the disk (e.g. security issues,
disk full, etc.). Should still let the client know of such issues.

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