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/05/28 12:54:00 UTC
[jira] [Created] (IGNITE-13088) Improve exception when cache not
exists after client restart
Ilya Kasnacheev created IGNITE-13088:
----------------------------------------
Summary: 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
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-8.7.10.jar:8.7.10]
at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1580) ~[ignite-core-8.7.10.jar:8.7.10]
at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:634) ~[ignite-core-8.7.10.jar:8.7.10]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)