max-entries=-1 is not accepted for overridden named cache.

[ulablue]

Hello,

I have below configuration in standalone.xml. The custom cache named "data-local-query" defines the max-entries="-1" which is valid as per documentation to have unlimited entries.

But it seems there is a conflict with default local cache and WildFly startup error. Why cannot I define max-entries="-1" to override default one ?

Eviction maxEntries value cannot be less than or equal to zero if eviction is enabled

standalone.xml

            <cache-container name="hibernate" default-cache="local-query" module="org.hibernate.infinispan">

                <local-cache name="entity">

                    <transaction mode="NON_XA"/>

                    <eviction strategy="LRU" max-entries="10000"/>

                    <expiration max-idle="100000"/>

                </local-cache>

                <local-cache name="local-query">

                    <eviction strategy="LRU" max-entries="10000"/>

                    <expiration max-idle="100000"/>

                </local-cache>

                 <local-cache name="data-local-query">

                    <eviction strategy="LRU" max-entries="-1"/>

                    <expiration max-idle="14400" interval="20000" lifespan="86400000"/>

                </local-cache>

                <local-cache name="timestamps"/>

            </cache-container>

log error

2017-04-19 18:00:27,215 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.infinispan.hibernate.data-local-query.config: org.jboss.msc.service.StartException in service jboss.infinispan.hibernate.data-local-query.config: org.infinispan.commons.CacheConfigurationException: Eviction maxEntries value cannot be less than or equal to zero if eviction is enabled

Caused by: org.infinispan.commons.CacheConfigurationException: Eviction maxEntries value cannot be less than or equal to zero if eviction is enabled

        at org.infinispan.configuration.cache.EvictionConfigurationBuilder.validate(EvictionConfigurationBuilder.java:108)

        at org.infinispan.configuration.cache.ConfigurationBuilder.validate(ConfigurationBuilder.java:203)

        at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:246)

        at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:236)

        at org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder.start(ConfigurationBuilder.java:79)

        at org.wildfly.clustering.service.AsynchronousServiceBuilder$1.run(AsynchronousServiceBuilder.java:102)

[jholusa]

Hi Ulab,

based on your configuration code snippet, I guess you don't use version 9.x, but something <= 8.2

Your setup is actually wrong, you probably misread a bit. When you look into the documentation here [1], in the last row you see exactly configuration you used and the documentation says that it's an configuration error. The -1 really means no eviction, but you also must not provide the "strategy" attribute. When you think about it, it semantically doesn't make sense. You tell Infinispan that you don't want eviction at all (by providing -1), but you also specify the strategy for eviction.

Conclusion: Remove the strategy attribute and you're good to go

Cheers,

Jiri

[1] http://infinispan.org/docs/8.2.x/user_guide/user_guide.html#more_defaults

[ulablue]

yes thanks. I realized it later.

But one more question. Do you think if eviction is set to no, even the expiration thread will not run ? Because I need expiration but not eviction for this region.

Thanks.

[ulablue]

I tried myself and with above config and expiration happens even without any eviction.

[jholusa]

Oh, I'm sorry for not responding, I totally missed your last post

Yes, it's definitely possible, expiration and eviction are basically unrelated functions (though they may seem similar), you can use any combination independently.