[jboss-jira] [JBoss JIRA] (WFLY-10404) Review/revise 2lc caching design

[Scott Marlow (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow updated WFLY-10404:
--------------------------------
    Description: 
Review cache isolation, cache region factories, override ISPN default behavior to handle more efficient names, updates to infinispan-hibernate-cache-spi, app configuration choices for choosing different strategies.

* Avoid the ByteString byte length limitation of 255 ([https://github.com/infinispan/infinispan/commit/046517fc0829bb0a1768169e549e8e5f6b2b8ea2]) in region name prefix + region name as cache key.
* Enhance the org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator to improve caching for:
** container managed persistence units
**  non-container-managed persistence unit (e.g. native Hibernate or app calls into javax.persistence.Persistence.createEntityManagerFactory())
**  Update WildFlyCustomRegionFactoryInitiator to start an Infinispan cache by default (e.g. if no other caching config props are specified) that works with clustering/standalone WF use. 
*** Currently, Hibernate defaults the 2lc on but that fails when the Infinispan cache is not automatically started, so WildFlyCustomRegionFactoryInitiator defaults caching off.
*** If this is not possible, then keep the current WildFlyCustomRegionFactoryInitiator logic to default Hibernate caching off, unless the app requests caching via configuration settings.

 

  was:
Review cache isolation, cache region factories, override ISPN default behavior to handle more efficient names, updates to infinispan-hibernate-cache-spi, app configuration choices for choosing different strategies.

* Avoid the ByteString byte length limitation of 255 ([https://github.com/infinispan/infinispan/commit/046517fc0829bb0a1768169e549e8e5f6b2b8ea2]) in region name prefix + region name as cache key.
* Enhance the org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator to improve caching for:
** container managed persistence units
**  non-container-managed persistence unit (e.g. native Hibernate or app calls into javax.persistence.Persistence.createEntityManagerFactory())
**  Update WildFlyCustomRegionFactoryInitiator to start an Infinispan cache by default (e.g. if no other caching config props are specified) that works with clustering/standalone WF use. 
*** Currently, Hibernate defaults the 2lc on but that fails when the Infinispan cache is not automatically started, so WildFlyCustomRegionFactoryInitiator defaults caching off.

 



> Review/revise 2lc caching design
> --------------------------------
>
>                 Key: WFLY-10404
>                 URL: https://issues.jboss.org/browse/WFLY-10404
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering, JPA / Hibernate
>    Affects Versions: 13.0.0.Beta1
>            Reporter: Scott Marlow
>            Assignee: Paul Ferraro
>             Fix For: 14.0.0.CR1
>
>
> Review cache isolation, cache region factories, override ISPN default behavior to handle more efficient names, updates to infinispan-hibernate-cache-spi, app configuration choices for choosing different strategies.
> * Avoid the ByteString byte length limitation of 255 ([https://github.com/infinispan/infinispan/commit/046517fc0829bb0a1768169e549e8e5f6b2b8ea2]) in region name prefix + region name as cache key.
> * Enhance the org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator to improve caching for:
> ** container managed persistence units
> **  non-container-managed persistence unit (e.g. native Hibernate or app calls into javax.persistence.Persistence.createEntityManagerFactory())
> **  Update WildFlyCustomRegionFactoryInitiator to start an Infinispan cache by default (e.g. if no other caching config props are specified) that works with clustering/standalone WF use. 
> *** Currently, Hibernate defaults the 2lc on but that fails when the Infinispan cache is not automatically started, so WildFlyCustomRegionFactoryInitiator defaults caching off.
> *** If this is not possible, then keep the current WildFlyCustomRegionFactoryInitiator logic to default Hibernate caching off, unless the app requests caching via configuration settings.
>  



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)