[ https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331987#comment-16331987 ]
Ilya Kasnacheev commented on IGNITE-2766: ----------------------------------------- No, I still don't get it. New Ignite cluster just doesn't have the 'TEST' cache. Even if it did, it would be a different cache (if not for persistence). Eventually with a different cache config. I will try to update the test with a working example. > 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 > > 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)