[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309904#comment-15309904
]
Jon Ekdahl commented on IGNITE-2766:
------------------------------------
The issue description refers to "special logic" but does not mention how this
logic would be implemented. Is there a "known workaround" to this problem that
users of Ignite 1.5.x can deploy?
> 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.7
>
>
> 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)
