Denis Magda created IGNITE-3719:
-----------------------------------
Summary: Automatically renew reference to internal IgniteCache
impl after client node reconnect
Key: IGNITE-3719
URL: https://issues.apache.org/jira/browse/IGNITE-3719
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Denis Magda
When a client node automatically reconnects to a cluster that has been
restarted from scratch, the client side can start generating the following
exceptions
{{IllegalStateException: Cache has been closed or destroyed: cache"}}.
To workaround this exception after the reconnect the client node has to renew
its references to closed {{IgniteCaches}} using either {{Ignite.cache(...)}} or
{{Ignite.getOrCreateCache(...)}} APIs.
This is not user friendly and Ignite can renew this references in its
implementation automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
