[ https://issues.apache.org/jira/browse/IGNITE-13088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127132#comment-17127132 ]
Alexander Korenshteyn commented on IGNITE-13088: ------------------------------------------------ [~ilyak] Fix looks good. > 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 > Time Spent: 10m > 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)