Hi Val, Sorry for the delay, I will work on the fix on weekend.
Thanks, On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <rishiyag...@gmail.com> wrote: > Hi Val, > > I will work on it in my spare time.. > > Take Care, > Rishi > > > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > > Hi Rishi, > > > > Can you please assign the ticket to yourself and create a pull request as > > described in [1]? > > > > Let's follow the process :) > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > > > -Val > > > > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <rishiyag...@gmail.com> > > wrote: > > > >> Hi Val, > >> > >> The fix which we applied as follows with SpringCacheManager - > >> > >> 1) Design was to listen for ignite re connect event > >> 2) And clear the cache on reconnect > >> > >> See the following code below and let us know if this is helpful - > >> > >> In afterPropertiesSet - > >> > >> //Handles the reconnect event, on server crashes OR network failure, > client > >> connects to server and > >> // destroy the cache > >> IgnitePredicate<DiscoveryEvent> lsnr = iEvt -> { > >> LOGGER.info("Received discovery event [iEvt=" + iEvt.name() + > >> ", > >> discovery=" + iEvt.shortDisplay() + ']'); > >> > >> caches.keySet().forEach(key -> { > >> ignite.destroyCache(key); > >> caches.remove(key); > >> } ); > >> > >> > >> > >> Let me know if you see any side effects with the fix. > >> > >> Thanks, > >> Rishi > >> > >> > >> > >> -- > >> View this message in context: http://apache-ignite- > >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache- > >> Manager-ReConnect-Issue-tp15362.html > >> Sent from the Apache Ignite Developers mailing list archive at > Nabble.com. > >> > -- Rishi Yagnik
