Why the difference between configurations of the Infinispan subsystem in EAP 7.x

Solution Verified - Updated -

Issue

We are upgrading JBoss EAP from 7.0 to 7.2.4. The new setup is working fine in lower environments. In the Infinispan subsystem, we see a small variation in the configuration for the below section. Can be clarified the impact of this change?

  • Current 7.0 production setup:

        <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="timestamps"/>
        </cache-container>
    
  • New 7.2.4 production setup:

        <cache-container name="hibernate" default-cache="local-query" module="org.infinispan.hibernate-cache">
            <local-cache name="entity">
                <transaction mode="NON_XA"/>
                <object-memory size="10000"/>
                <expiration max-idle="100000"/>
            </local-cache>
            <local-cache name="local-query">
                <object-memory size="10000"/>
                <expiration max-idle="100000"/>
            </local-cache>
            <local-cache name="timestamps"/>
        </cache-container>
    

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content