You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2020/06/08 09:16:00 UTC

[jira] [Updated] (IGNITE-13088) Improve exception when cache not exists after client restart

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

Ilya Kasnacheev updated IGNITE-13088:
-------------------------------------
    Ignite Flags:   (was: Release Notes Required)

> Improve exception when cache not exists after client restart
> ------------------------------------------------------------
>
>                 Key: IGNITE-13088
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13088
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.8.1
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>            Priority: Minor
>             Fix For: 2.9
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> After IGNITE-2766 it's possible to get the following error after client reconnects to fresh cluster, if the cache which cache proxy was pointing at no longer exists:
> {code}
> java.lang.NullPointerException: null
>         at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.checkProxyIsValid(GatewayProtectedCacheProxy.java:1563) ~[ignite-core.jar]
>         at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1580) ~[ignite-core.jar]
>         at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:634) ~[ignite-core.jar]
> {code}



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