[
https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170392#comment-16170392
]
Valentin Kulichenko commented on IGNITE-2786:
---------------------------------------------
[~bbarin], node restart is not needed because Ignite client reconnects
automatically. The only issue here is that {{IgniteCache}} instance acquired
before the disconnection can't be used after the reconnect. So in my view the
only thing required is to clean up {{SpringCacheManager#caches}} map if
disconnect happens (Ignite provides special event for this, so it's easy to
create a listener).
> SpringCache doesn't survive client reconnect
> --------------------------------------------
>
> Key: IGNITE-2786
> URL: https://issues.apache.org/jira/browse/IGNITE-2786
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
>
> After a client disconnects and reconnects with new ID, Spring caching can't
> be used, because existing cache instance are closed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
