[jira] [Commented] (IGNITE-3719) Automatically renew reference to internal IgniteCache impl after client node reconnect

["Alper Tekinalp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614580#comment-15614580 ] 

Alper Tekinalp commented on IGNITE-3719:
----------------------------------------

Hi. 

We have multiple server and client nodes. And clients connect to/disconnect from cluster regularly. And regularly in our server applications we are getting the same IllegalStateException: Cache has been closed or destroyed: cache error. Is there a specific reason for that error? Can regularly starting and stopping client daemons cause that error or server side?

Regards.


> 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)