You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Bill Venners (JIRA)" <ji...@apache.org> on 2007/08/12 05:07:47 UTC
[jira] Created: (RIVER-235) Redo log locking strategy in mahalo
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]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-235) Redo log locking strategy in mahalo
Posted by "Bill Venners (JIRA)" <ji...@apache.org>.
[ 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.