[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457624#comment-16457624
]
Pavel Pereslegin commented on IGNITE-2766:
------------------------------------------
Hello [~ilyak], [~vkulichenko].
I'm faced with the fact that now IgniteCacheRestartingException can be thrown
after IgniteCache#destroy method was called on the server node when we continue
working with this cache asynchronously. Seems it's not right because we
destroying cache.
How do yout think - is it ok to change GatewayProtectedCacheProxy#onEnter from
{code:java}
checkProxyIsValid(gate(), true) // tryRestart = true
{code}
to something like
{code:java}
checkProxyIsValid(gate(), context().localNode().isClient()) // tryRestart =
true only on client node
{code}
?
I checked tests ClientReconnectAfterClusterRestartTest,
IgniteCacheQueryCacheDestroySelfTest and they works well with such change.
> 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)
