You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mnemonic.apache.org by "Wang, Gang (JIRA)" <ji...@apache.org> on 2018/08/09 05:14:00 UTC
[jira] [Resolved] (MNEMONIC-499) The refBreak function should be
prevented from reclaimable referred durable object
[ https://issues.apache.org/jira/browse/MNEMONIC-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wang, Gang resolved MNEMONIC-499.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.12.0
Resolved
> The refBreak function should be prevented from reclaimable referred durable object
> ----------------------------------------------------------------------------------
>
> Key: MNEMONIC-499
> URL: https://issues.apache.org/jira/browse/MNEMONIC-499
> Project: Mnemonic
> Issue Type: Sub-task
> Components: Core
> Affects Versions: 0.12.0
> Reporter: Wang, Gang
> Assignee: Wang, Gang
> Priority: Major
> Fix For: 0.12.0
>
>
> The The referring durable object would crash if the referred durable object has been handled by refbreak functionality that is reclaimable. so there should be a guard code to check up the autoreclaim state and reject refbreak if that state is true.
> This approach does not ensure all descendants to get protected, it requires developer to follow the reclaim protocol before actually call the refbreak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)