[IGNITE-13088] Improve exception when cache not exists after client restart

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.9
• Component/s: cache
• Release Note: Fixed potential NullPointerException on cache operations after client reconnect.
• Assignee: Ilya Kasnacheev
• Reporter: Ilya Kasnacheev
• Created: 28/May/20 12:53
• Updated: 08/Jun/20 09:15
• Resolved: 08/Jun/20 09:15

Description

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:

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]

Issue Links

• is caused by: IGNITE-2766 Cache instance is closed when client disconnects
• links to: GitHub Pull Request #7873