river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Venners (JIRA)" <j...@apache.org>
Subject [jira] Updated: (RIVER-235) Redo log locking strategy in mahalo
Date Sun, 12 Aug 2007 03:17:43 GMT

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

Bill Venners updated RIVER-235:
-------------------------------

     Bugtraq ID: 4962981  (was: 4962981])
    Description: 
Bugtraq ID [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4962981]

Bug 4365178 was caused by a race condition in how logs are updated. That bug was
closed because the specific problem scenario was fixed in the 
latest software release. The race condition analysis did bring up the fact 
that mahalo's log locking strategy could cause similar problems under 
other scenarios.

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




> Redo log locking strategy in mahalo
> -----------------------------------
>
>                 Key: RIVER-235
>                 URL: https://issues.apache.org/jira/browse/RIVER-235
>             Project: River
>          Issue Type: Bug
>          Components: com_sun_jini_mahalo
>    Affects Versions: jtsk_2.0
>            Reporter: Bill Venners
>            Priority: Minor
>
> Bugtraq ID [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4962981]
> Bug 4365178 was caused by a race condition in how logs are updated. That bug was
> closed because the specific problem scenario was fixed in the 
> latest software release. The race condition analysis did bring up the fact 
> that mahalo's log locking strategy could cause similar problems under 
> other scenarios.

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