title: Using Ignite for Hibernate 2nd level cache with S3 discovery, changes are not progagated
body: <p>We have deployed a cluster to AWS configured to use Ignite as a hibernate 2nd level cache, and we're using S3 discovery. On startup we can see the nodes do connect to each other correctly.</p>
  
  <p>However, when a hibernate entity is updated on one server, the change is not propagated through the cluster so other servers continue to have the old value.</p>
  
  <p>Here is a snippet of our ignite config..
  ```
      
           
          
          
          
      </p>
  
  <pre><code>&lt;!-- Basic configuration for transactional cache. --&gt;
  &lt;bean id="transactional-cache" class="org.apache.ignite.configuration.CacheConfiguration" abstract="true"&gt;
      &lt;property name="cacheMode" value="REPLICATED"/&gt;
      &lt;property name="atomicityMode" value="TRANSACTIONAL"/&gt;
      &lt;property name="writeSynchronizationMode" value="FULL_ASYNC"/&gt;
      &lt;property name="backups" value="0"/&gt;
  &lt;/bean&gt;
  
  &lt;bean id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration" &gt;
      &lt;property name="discoverySpi" ref="discoverySpi"/&gt;
      &lt;property name="gridName" value="hibernate-grid"/&gt;
      &lt;property name="cacheConfiguration"&gt;
          &lt;list&gt;
              &lt;bean parent="transactional-cache"&gt;
                  &lt;property name="name" value="hibernate.io.milton.vfs.db.Auditable"/&gt;
              &lt;/bean&gt;
  </code></pre>
  
  <p>```</p>
  
  <p>The exact same application code, when configured with hazelcast 2nd level cache, does work.</p>
  
  <p>I'm sure there's just something wrong with our config. Can anyone suggest a pointer?</p>