Instead of adding new feature; can we address the issue with VM exit. The
auto-reconnect feature does cache close without exiting the VM.
-Anil.
On Wed, Mar 21, 2018 at 9:48 AM, Jinmei Liao <jil...@pivotal.io> wrote:
> We would like to allow users to import a new set of cluster configuration
> with running servers as long as we make sure these servers are vanilla
> servers (servers that are just started with nothing in it). Now since the
> servers are already up, caches are already created, we will need to
> re-create the cache with the new xml received from the locator. Originally
> our implementation on the servers boils down to:
>
> cache.close("Re-create Cache", true, true);
>
> GemFireCacheImpl.create(oldDs, cacheConfig);
>
>
> but the cache.close call eventually leads to a VM exit (somehow in the
> DUunit VM, it doesn not), so this does not work with real application
> environment. Now we are wondering is there a safe to recreate the cache
> instance with a new set of properties/cacheXml without triggering the
> entire shutdown sequence?
>
>
> --
> Cheers
>
> Jinmei
>
