August 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8388) Entity with @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) fails if cache is configured as simple cache

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-8388?page=com.atlassian.jira.plugin... ] Paul Ferraro updated ISPN-8388: ------------------------------- Priority: Critical (was: Major) > Entity with @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) fails if cache is configured as simple cache > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8388 > URL: https://issues.redhat.com/browse/ISPN-8388 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.1.1.Final, 9.2.0.Alpha1 > Reporter: Paul Ferraro > Priority: Critical > > The Infinispan region factory needs to explicitly disable the simple cache optimization for cache regions that will use the NONSTRICT_READ_WRITE concurrency strategy. > This issue is particularly troublesome for WildFly where the simple cache optimization is automatically enabled for non-transactional, non-persistent local caches. > {noformat} > 2017-10-06 14:56:36,221 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 19) MSC000001: Failed to start service jboss.persistenceunit."harmonyserver.sar#IpsDb": org.jboss.msc.service.StartException in service jboss.persistenceunit."harmonyserver.sar#IpsDb": javax.persistence.PersistenceException: [PersistenceUnit: IpsDb] Unable to build Hibernate SessionFactory > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:179) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:121) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:193) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: javax.persistence.PersistenceException: [PersistenceUnit: IpsDb] Unable to build Hibernate SessionFactory > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:954) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:882) > at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:161) > ... 7 more > Caused by: java.lang.UnsupportedOperationException: ISPN000376: Interceptor stack is not supported in simple cache > at org.infinispan.cache.impl.SimpleCacheImpl.removeInterceptor(SimpleCacheImpl.java:952) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.removeInterceptor(AbstractDelegatingAdvancedCache.java:85) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.prepareForVersionedEntries(BaseTransactionalDataRegion.java:154) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.createAccessDelegate(BaseTransactionalDataRegion.java:122) > at org.hibernate.cache.infinispan.entity.EntityRegionImpl.buildAccessStrategy(EntityRegionImpl.java:50) > at org.hibernate.internal.SessionFactoryImpl.determineEntityRegionAccessStrategy(SessionFactoryImpl.java:624) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:332) > at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:879) > ... 9 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8388) Entity with @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) fails if cache is configured as simple cache

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-8388?page=com.atlassian.jira.plugin... ] Paul Ferraro reassigned ISPN-8388: ---------------------------------- Assignee: (was: Galder Zamarreño) > Entity with @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) fails if cache is configured as simple cache > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8388 > URL: https://issues.redhat.com/browse/ISPN-8388 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.1.1.Final, 9.2.0.Alpha1 > Reporter: Paul Ferraro > Priority: Major > > The Infinispan region factory needs to explicitly disable the simple cache optimization for cache regions that will use the NONSTRICT_READ_WRITE concurrency strategy. > This issue is particularly troublesome for WildFly where the simple cache optimization is automatically enabled for non-transactional, non-persistent local caches. > {noformat} > 2017-10-06 14:56:36,221 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 19) MSC000001: Failed to start service jboss.persistenceunit."harmonyserver.sar#IpsDb": org.jboss.msc.service.StartException in service jboss.persistenceunit."harmonyserver.sar#IpsDb": javax.persistence.PersistenceException: [PersistenceUnit: IpsDb] Unable to build Hibernate SessionFactory > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:179) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:121) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:193) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: javax.persistence.PersistenceException: [PersistenceUnit: IpsDb] Unable to build Hibernate SessionFactory > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:954) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:882) > at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:161) > ... 7 more > Caused by: java.lang.UnsupportedOperationException: ISPN000376: Interceptor stack is not supported in simple cache > at org.infinispan.cache.impl.SimpleCacheImpl.removeInterceptor(SimpleCacheImpl.java:952) > at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.removeInterceptor(AbstractDelegatingAdvancedCache.java:85) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.prepareForVersionedEntries(BaseTransactionalDataRegion.java:154) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.createAccessDelegate(BaseTransactionalDataRegion.java:122) > at org.hibernate.cache.infinispan.entity.EntityRegionImpl.buildAccessStrategy(EntityRegionImpl.java:50) > at org.hibernate.internal.SessionFactoryImpl.determineEntityRegionAccessStrategy(SessionFactoryImpl.java:624) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:332) > at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:879) > ... 9 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11731) Add blockhound to query module

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11731?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11731: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8613 > Add blockhound to query module > ------------------------------ > > Key: ISPN-11731 > URL: https://issues.redhat.com/browse/ISPN-11731 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > > We need to make sure that various parts of the query module do not run blocking code in non blocking threads. We should add blockhound and make sure to fix all violations by running on the blocking thread or appropriately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11731) Add blockhound to query module

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11731?page=com.atlassian.jira.plugi... ] Work on ISPN-11731 started by Gustavo Fernandes. ------------------------------------------------ > Add blockhound to query module > ------------------------------ > > Key: ISPN-11731 > URL: https://issues.redhat.com/browse/ISPN-11731 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > > We need to make sure that various parts of the query module do not run blocking code in non blocking threads. We should add blockhound and make sure to fix all violations by running on the blocking thread or appropriately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11731) Add blockhound to query module

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11731?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11731: ------------------------------------- Status: Open (was: New) > Add blockhound to query module > ------------------------------ > > Key: ISPN-11731 > URL: https://issues.redhat.com/browse/ISPN-11731 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > > We need to make sure that various parts of the query module do not run blocking code in non blocking threads. We should add blockhound and make sure to fix all violations by running on the blocking thread or appropriately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11731) Add blockhound to query module

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11731?page=com.atlassian.jira.plugi... ] Gustavo Fernandes reassigned ISPN-11731: ---------------------------------------- Assignee: Gustavo Fernandes (was: Will Burns) > Add blockhound to query module > ------------------------------ > > Key: ISPN-11731 > URL: https://issues.redhat.com/browse/ISPN-11731 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > > We need to make sure that various parts of the query module do not run blocking code in non blocking threads. We should add blockhound and make sure to fix all violations by running on the blocking thread or appropriately. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11614) PersistenceMarshaller should utilise an independent SerializationContext for user types

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11614?page=com.atlassian.jira.plugi... ] Ryan Emerson commented on ISPN-11614: ------------------------------------- Isolating the user and internal serialization contexts introduces a binary incompatibility between Infinispan 11 and 12 stores, as previously user objects marshalled via protostream were not wrapped in a `MarshallableUserObject` wrapper. To overcome this incompatibility, it's necessary for existing Infinispan 11 stores to be converted on startup. Currently there is no way of determining the version of Infinispan used to create Jdbc and RocksDB store's, therefore we need to add this capability via https://issues.redhat.com/browse/ISPN-12204 and https://issues.redhat.com/browse/ISPN-12205. > PersistenceMarshaller should utilise an independent SerializationContext for user types > --------------------------------------------------------------------------------------- > > Key: ISPN-11614 > URL: https://issues.redhat.com/browse/ISPN-11614 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > If a user configures a SerializationContextInitializer it is currently registered to the same SerializationContext as the persistent internal types. This means that it is possible for a user to reference internal protobuf message types in their .proto files. We should utilise a seperate SerializationContext to ensure that these types are truly indepdenent. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12205) Add RocksDB Meta Column Family

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-12205: ----------------------------------- Summary: Add RocksDB Meta Column Family Key: ISPN-12205 URL: https://issues.redhat.com/browse/ISPN-12205 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 12.0.0.Dev01 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 12.0.0.Dev02 Currently there is no way to determine what version of Infinispan created a RocksDb store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced. We should add an additional column family to store such metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12204) Add JDBC Meta Table

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-12204: ----------------------------------- Summary: Add JDBC Meta Table Key: ISPN-12204 URL: https://issues.redhat.com/browse/ISPN-12204 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Affects Versions: 12.0.0.Dev01 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 12.0.0.Dev02 Currently there is no way to determine what version of Infinispan created a Jdbc store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced. Similarly it's not possible for us to verify that the configured number of segments match those present in an existing store. We should add an additional table to store such metadata. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12186) Upgrade to Hibernate Search 6.0.0.Beta9

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12186?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12186: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8612 > Upgrade to Hibernate Search 6.0.0.Beta9 > --------------------------------------- > > Key: ISPN-12186 > URL: https://issues.redhat.com/browse/ISPN-12186 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Yoann Rodière > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Dev02 > > > TODO: > * Upgrade the Hibernate Search dependency (obviously); be warned the Lucene dependency is now 8.6.0 > * Handle [deprecations and breaking changes|https://in.relation.to/2020/08/03/hibernate-search-6-0-0-Beta9/#breaking_changes] > * Simplify the configuration properties generated by Infinispan and passed to Hibernate Search; see [here|https://in.relation.to/2020/08/03/hibernate-search-6-0-0-Beta9/#simpler-configuration-scheme]. > * Simplify the generation of IDs: {{org.hibernate.search.mapper.pojo.work.spi.PojoIndexer}} now allows passing the routing key explicitly (in our case, {{String.valueOf(segmentId)}}), so our custom implementation of {{RoutingKeyBridge}} (which relies on a hack) is no longer necessary. > * As a result of the previous item, we can also get rid of the hack that concatenates the segment ID to the document ID; see ISPN-12170. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2020