Update to near cache value is not reflected in the other near cache

Question

Hi,
I have a cluster of two weblogic servers running within them tangosol cache. I also have two seperate tangosol servers running on the same two servers.
When I make an update on the tangosol cache on one of the weblogic application, unfortunately the update is not picked up by the other weblogic application tangosol cache.
What do I need to do so that all updates are available in all the tangosol cache?
example below:
initial:
server1: weblogic tangosol near cache, key = "One", Value = null
server2: weblogic tangosol near cache, key = "One", Value = null
update on server1;
server1: weblogic tangosol near cache, key = "One", Value = "New York"
server2: weblogic tangosol near cache, key = "One", Value = null <- still null (?)
Why is the value on server2 not updated also?
Thanks.
The tangosol configuration is a near distributed cache. The xml is below. Thanks.
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<!--
Caches with any name will be created as default replicated.
-->
<cache-mapping>
<cache-name>*</cache-name>
<scheme-name>default-near</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<!--
Default simple Near caching scheme with default eviction local cache
in the front-tier and a non-expiring distributed cache in the back-tier.
-->
<near-scheme>
<scheme-name>default-near</scheme-name>
<front-scheme>
<local-scheme>
<scheme-ref>default-eviction</scheme-ref>
</local-scheme>
</front-scheme>
<back-scheme>
<distributed-scheme>
<scheme-ref>default-distributed</scheme-ref>
</distributed-scheme>
</back-scheme>
<!--
invalidation auto = all changes in back caches gets notified
present = subscribes to only changes thats held in near cache
-->
<invalidation-strategy>auto</invalidation-strategy>
<!-- the cache server starts does not start all the schemes -->
<autostart>false</autostart>
</near-scheme>
<!--
Default Distributed caching scheme.
-->
<distributed-scheme>
<scheme-name>default-distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<class-scheme>
<scheme-ref>default-backing-map</scheme-ref>
</class-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
<!--
Default backing map scheme definition used by all the caches that do
not require any eviction policies
-->
<class-scheme>
<scheme-name>default-backing-map</scheme-name>
<class-name>com.tangosol.util.SafeHashMap</class-name>
<init-params></init-params>
</class-scheme>
<!--
Default eviction policy scheme.
-->
<local-scheme>
<scheme-name>default-eviction</scheme-name>
<eviction-policy>HYBRID</eviction-policy>
<high-units>100000</high-units>
<low-units>0</low-units>
<expiry-delay>0</expiry-delay>
<flush-delay>0</flush-delay>
<cachestore-scheme></cachestore-scheme>
</local-scheme>
</caching-schemes>
</cache-config>

Answer 1

We can certainly set up a call to discuss what you are seeing. Please email [email protected] with your phone number and other information to set up the call.
The more information that you can provide in advance (on the forum or by email), the better. For example, send your configuration settings (cache configuration, cluster configuration) files.
Peace.