You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mnemonic.apache.org by "Xiaojin Jiao (Jira)" <ji...@apache.org> on 2021/02/14 19:16:00 UTC

[jira] [Commented] (MNEMONIC-588) Re-design the memory service selection mechanism

    [ https://issues.apache.org/jira/browse/MNEMONIC-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284482#comment-17284482 ] 

Xiaojin Jiao commented on MNEMONIC-588:
---------------------------------------

With further testing and validation, we figured out a way to keep the extension mechanism for the higher version JDK. The open tickets to replacing the Utils.getNonVolatileMemoryAllocatorService and Utils.getVolatileMemoryAllocatorService calls will be closed, and more new tickets will be submitted soon.   

> Re-design the memory service selection mechanism
> ------------------------------------------------
>
>                 Key: MNEMONIC-588
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-588
>             Project: Mnemonic
>          Issue Type: New Feature
>          Components: Memory-Service
>    Affects Versions: 0.14.0
>            Reporter: Wang, Gang
>            Assignee: Xiaojin Jiao
>            Priority: Major
>             Fix For: 0.14.0
>
>
> The memory service loading relies on the old JDK extension mechanism that has got removed in JDK10 and later, please refer to the following linked page.
> [https://docs.oracle.com/javase/10/migrate/toc.htm#JSMIG-GUID-2C896CA8-927C-4381-A737-B1D81D964B7B]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)