[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198771#comment-16198771
]
Ilya Kasnacheev commented on IGNITE-2766:
-----------------------------------------
When operation hits a closed cache proxy, instead of throwing exception we
should try to retrieve cache with the same name from KernalContext.
If that it successful, we update internal state and serve the operation as if
the cache is always open.
Obviously it means that there was a period of time when this cache object won't
be valid, we're teaching bad habits a bit, but with common try-catch-wait-retry
loops it should work OK.
> Cache instance is closed when client disconnects
> ------------------------------------------------
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Ilya Kasnacheev
>
> In case client disconnects and reconnects after network timeout (i.e., with a
> new ID), all cache instances acquired by this client are closed and are not
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
