[
https://issues.apache.org/jira/browse/IGNITE-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170507#comment-16170507
]
Bruno Barin commented on IGNITE-2786:
-------------------------------------
[~vkulichenko], if you really uses SpringCache with annotations, it will end up
using AbstractCacheInvoker which holds references to the caches as well, as you
can see in this stack trace on my application:
java.lang.IllegalStateException: Cache has been closed or destroyed: XYZ
…gnite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164)
…ite.internal.processors.cache.IgniteCacheProxy.onEnter(IgniteCacheProxy.java:2727)
….ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1189)
org.apache.ignite.cache.spring.SpringCache.get(SpringCache.java:57)
…framework.cache.interceptor.AbstractCacheInvoker.doGet(AbstractCacheInvoker.java:71)
…work.cache.interceptor.CacheAspectSupport.findInCaches(CacheAspectSupport.java:537)
…rk.cache.interceptor.CacheAspectSupport.findCachedItem(CacheAspectSupport.java:503)
…framework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:389)
…framework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:327)
…ingframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:61)
> 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)
