Ah, OK, it should really be disabled on Lucene caches:

                <replicated-cache name="LuceneIndexesMetadata" mode="SYNC">
                    <transaction mode="NONE"/>
                    <eviction strategy="NONE"/>
                    <file-store preload="true" purge="false"/>
                </replicated-cache>
                <replicated-cache name="LuceneIndexesData" mode="SYNC">
                    <transaction mode="NONE"/>
                    <eviction strategy="NONE"/>
                    <file-store preload="true" purge="false"/>
                </replicated-cache>
                <replicated-cache name="LuceneIndexesLocking" mode="SYNC">
                    <transaction mode="NONE"/>
                    <eviction strategy="NONE"/>
                    <file-store preload="false" purge="true"/>
                </replicated-cache>

Horrible err msg ...

On Nov 22, 2012, at 12:53 PM, Ales Justin <ales.justin@gmail.com> wrote:

I was changing cache config a bit, and got this:
* https://gist.github.com/4130728

   private static void verifyCacheHasNoEviction(AdvancedCache<?, ?> cache) {
      if (cache.getConfiguration().getEvictionStrategy().isEnabled())
         throw new IllegalArgumentException("DistributedSegmentReadLocker is not reliable when using a cache with eviction enabled, disable eviction on this cache instance");
   }


How do you then handle memory overflow on no-eviction caches?


-Ales