You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/08/21 19:19:00 UTC

[jira] [Commented] (IGNITE-8486) Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK version

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

Andrey Gura commented on IGNITE-8486:
-------------------------------------

I remember that fix did'nt solve the problem. So path is cancelled.

> Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK version
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8486
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8486
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Stanislav Lukyanov
>            Assignee: Stanislav Lukyanov
>            Priority: Major
>             Fix For: 2.7
>
>         Attachments: jsr166-to-ignite.diff
>
>
> Ignite still uses copies of several JSR 166 (j.u.concurrent) classes in it's sources. Those copies are now outdated compared to the latest versions used in JDK.
> In particular, `ConcurrentLinkedDeque` has received a couple of correctness fixes recently (https://bugs.openjdk.java.net/browse/JDK-8188900, https://bugs.openjdk.java.net/browse/JDK-8189387). It would be good to have them in Ignite as well to protect ourselves from possible issues.
> The task is to update Ignite's `ConcurrentLinkedDeque8` to the latest version of `ConcurrentLinkedDeque`, although keeping compatibility with earlier Java version (e.g. JDK's version now uses Java 9's VarHandles which we can't use yet).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)