How to force write-behind store on cache node shutdown?

Question

Hi,
I built a small pilot project based on Coherence and now I test it for failover. I found replication issues with Distributed cache in the following scenario:
- start cache node 1 (JVM instance 1);
- connect Extend client to it and get 1 object from cache (only 1 object in the cache - loaded by CacheStore from DB);
- change the object and put it back (I use EntryProcessor for this);
- start cache node 2 (JVM instance 2);
- stop cache instance 1 (write-behind store wasn't invoked yet: write-delay = 2m);
- load/change the same object on node 2; all changes done on node 1 are lost.
My expectation was that cache will replicate its data between nodes when new member joins cache cluster. The backup count = 1 by default, right?
What should I do in order to prevent such behavior? Is it possible to force write-behind store on cache node shutdown event?
Thanks, Denis.
My cache-config, just in case:
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>AccountCache</cache-name>
<scheme-name>account-distributed</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>account-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
<init-params>
<init-param>
<param-type>String</param-type>
<param-value>account-pof-config.xml</param-value>
</init-param>
</init-params>
</serializer>
<backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-name>AccountDatabaseScheme</scheme-name>
<internal-cache-scheme>
<local-scheme>
<!--scheme-ref>default-eviction</scheme-ref-->
<eviction-policy>LRU</eviction-policy>
<high-units>0</high-units>
<expiry-delay>30m</expiry-delay>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>com.roox.bss.cache.store.AccountCacheStore</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>dburl_</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>user</param-value>
</init-param>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>password</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>
<write-delay>2m</write-delay>
<write-batch-factor>.5</write-batch-factor>
</read-write-backing-map-scheme>
</backing-map-scheme>
</distributed-scheme>
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>10</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address>localhost</address>
<port>9098</port>
<reuse-address>true</reuse-address>
<reusable>true</reusable>
</local-address>
</tcp-acceptor>
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
<init-params>
<init-param>
<param-type>String</param-type>
<param-value>account-pof-config.xml</param-value>
</init-param>
</init-params>
</serializer>
</acceptor-config>
<autostart>true</autostart>
</proxy-scheme>
</caching-schemes>
</cache-config>

Answer 1

solved with autostart=true