You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2018/05/03 12:21:00 UTC
[jira] [Commented] (IGNITE-2766) Cache instance is closed when
client disconnects
[ https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462358#comment-16462358 ]
Ilya Kasnacheev commented on IGNITE-2766:
-----------------------------------------
[~xtern] You can definitely do that. Shame on me it isn't implemented this way in the first place.
> 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
> Priority: Major
> Fix For: 2.5
>
>
> 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
(v7.6.3#76005)