[
https://issues.apache.org/jira/browse/IGNITE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331981#comment-16331981
]
Ilya Kasnacheev commented on IGNITE-2766:
-----------------------------------------
Yes, now I can see what is the real issue. It is as follows:
{code:java}
Exception in thread "main" java.lang.IllegalStateException: class
org.apache.ignite.internal.processors.cache.CacheStoppedException: Failed to
perform cache operation (cache is stopped): TEST
at
org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1656)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:659)
at ReconnectClient.main(ReconnectClient.java:36)
Caused by: class
org.apache.ignite.internal.processors.cache.CacheStoppedException: Failed to
perform cache operation (cache is stopped): TEST
... 4 more{code}
while IgniteClientDisconnectedException is expected!
> 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)
