[
https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952020#comment-15952020
]
Valentin Kulichenko commented on IGNITE-2786:
---------------------------------------------
[~ryagnik], can you please explain the fix? Why do you destroy the caches? In
my understanding we just need to clear {{caches}} map in {{SpringCacheManager}}
on {{DISCONNECTED}} event. This way if it reconnects, it will create new
{{SpringCache}} when needed. Agree? Also you should add tests to reproduce the
issue and then make sure that it is fixed by your change.
BTW, when you create a PR, please move the ticket to Patch Available. Please
refer to the development process description on our wiki for more details.
> 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
> Assignee: Rishi
> Fix For: 2.0
>
>
> 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.3.15#6346)
