[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186613#comment-15186613
]
Semen Boikov commented on IGNITE-2766:
--------------------------------------
Now after client reconenct we check that cache still exists and have the same
deploymentId (GridCacheProcessor.onReconnected). So even when client reconnects
with new ID old caches should work if they were not re-created while client was
disconnected. Maybe it can be improved and after reconnect we should ignore
deploymentId, but check that cache have the same configuration.
> 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
> Fix For: 1.6
>
>
> 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.3.4#6332)
