May 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8086) Remove deprecated methods from CacheEntry and MVCCEntry

by Radim Vansa (Jira)

[ https://issues.jboss.org/browse/ISPN-8086?page=com.atlassian.jira.plugin.... ] Radim Vansa reassigned ISPN-8086: --------------------------------- Assignee: Dan Berindei (was: Radim Vansa) > Remove deprecated methods from CacheEntry and MVCCEntry > ------------------------------------------------------- > > Key: ISPN-8086 > URL: https://issues.jboss.org/browse/ISPN-8086 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Major > > Remove StateChangingEntry iface as well -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8071) Remove Delta and DeltaAware interfaces

by Radim Vansa (Jira)

[ https://issues.jboss.org/browse/ISPN-8071?page=com.atlassian.jira.plugin.... ] Radim Vansa reassigned ISPN-8071: --------------------------------- Assignee: (was: Radim Vansa) > Remove Delta and DeltaAware interfaces > -------------------------------------- > > Key: ISPN-8071 > URL: https://issues.jboss.org/browse/ISPN-8071 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10208) Test result files not being generated

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10208?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10208: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6959, https://github.com/infinispan/infinispan/pull/6958, https://github.com/infinispan/infinispan/pull/6939 > Test result files not being generated > ------------------------------------- > > Key: ISPN-10208 > URL: https://issues.jboss.org/browse/ISPN-10208 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 10.0.0.Beta3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Test result files not being generated for most modules which use JUnit. This is masking test failures such as ISPN-10207. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10208) Test result files not being generated

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10208?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10208: ----------------------------------- Fix Version/s: 10.0.0.Beta4 9.4.14.Final (was: 10.0.0.Final) > Test result files not being generated > ------------------------------------- > > Key: ISPN-10208 > URL: https://issues.jboss.org/browse/ISPN-10208 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 10.0.0.Beta3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Test result files not being generated for most modules which use JUnit. This is masking test failures such as ISPN-10207. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10208) Test result files not being generated

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10208?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10208: ----------------------------------- Description: Test result files not being generated for most modules which use JUnit. This is masking test failures such as ISPN-10207. was:Test result files not being generated for Hibernate Cache 5.1 and Hibernate Cache 5.3 testsuites. This is masking test failures such as ISPN-10207. > Test result files not being generated > ------------------------------------- > > Key: ISPN-10208 > URL: https://issues.jboss.org/browse/ISPN-10208 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 10.0.0.Beta3 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Final > > > Test result files not being generated for most modules which use JUnit. This is masking test failures such as ISPN-10207. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9457) Async caches should provide a way to track replication time stats

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9457?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9457: ---------------------------------- Status: Pull Request Sent (was: Reopened) > Async caches should provide a way to track replication time stats > ----------------------------------------------------------------- > > Key: ISPN-9457 > URL: https://issues.jboss.org/browse/ISPN-9457 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication, JMX, reporting and management > Affects Versions: 9.3.1.Final > Reporter: Tristan Tarrant > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Async caches should offer the capability of measuring replication time. > This would probably involve the receiver sending an ack which would be used for stats accounting. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9457) Async caches should provide a way to track replication time stats

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9457?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9457: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Async caches should provide a way to track replication time stats > ----------------------------------------------------------------- > > Key: ISPN-9457 > URL: https://issues.jboss.org/browse/ISPN-9457 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication, JMX, reporting and management > Affects Versions: 9.3.1.Final > Reporter: Tristan Tarrant > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Async caches should offer the capability of measuring replication time. > This would probably involve the receiver sending an ack which would be used for stats accounting. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9027) Distinguishing multiple server Store configurations is impossible

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9027: ---------------------------------- Status: Pull Request Sent (was: Reopened) > Distinguishing multiple server Store configurations is impossible > ----------------------------------------------------------------- > > Key: ISPN-9027 > URL: https://issues.jboss.org/browse/ISPN-9027 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 9.2.1.Final > Reporter: Sebastian Laskawiec > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > Attachments: clustered.xml > > > h3. Problem description > One of our users reported that when using two Deployed Cache Stores, their configuration gets overridden and both behaves as if they had the same configuration. Here's an example: > {code} > <distributed-cache name="cassandracache1" owners="2" segments="256" mode="SYNC"> > <store name="store1" class="org.infinispan.persistence.cassandra.CassandraStore" preload="true"> > <property name="autoCreateKeyspace"> > true > </property> > <property name="keyspace"> > Infinispan > </property> > <property name="entryTable"> > InfinispanEntries > </property> > <property name="servers"> > 172.17.0.2[9042] > </property> > </store> > </distributed-cache> > <distributed-cache name="cassandracache2" owners="2" segments="256" mode="SYNC"> > <store name="store2" class="org.infinispan.persistence.cassandra.CassandraStore" preload="true"> > <property name="autoCreateKeyspace"> > true > </property> > <property name="keyspace"> > Infinispan > </property> > <property name="entryTable"> > InfinispanEntries1 > </property> > <property name="servers"> > 172.17.0.2[9042] > </property> > </store> > </distributed-cache> > {code} > Both caches ({{cassandracache1}} and {{cassandracache2}}) use the same {{entryTable}} which is set to {{InfinispanEntries1}}. > h3. Investigation > {{CacheStoreFactory}} implementation were created to fabricate Loader/Writer instance based on parsed configuration (via {{createInstance}} method). This method receives from {{PersistenceManagerImpl}} an instance of an {{AbstractStoreConfiguration}} (here's an example (1)) two times - once per each parsed configuration. The parsing part seems OK but we do not parse Cache Store Name, which makes differentiating both configuration impossible. > h3. Proposed fix > * Add {{name}} attribute to {{StoreConfiguration}}. > * Either add an explicit parameter to {{CacheStoreFactory#createInstance(StoreConfiguration cfg, String cacheStoreName)}} or scan for Cache Store name in both implementations ({{DeployedCacheStoreFactory}} and {{LocalClassLoaderCacheStoreFactory}}. > {code} > (1) AbstractStoreConfiguration [attributes=DeployedStoreConfiguration = [fetchPersistentState=false, purgeOnStartup=false, ignoreModifications=false, preload=true, shared=false, transactional=false, maxBatchSize=100, properties={keyspace=Infinispan, connectionPool.poolTimeoutMillis=5, entryTable=InfinispanEntries, connectionPool.idleTimeoutSeconds=120, connectionPool.heartbeatIntervalSeconds=30, autoCreateKeyspace=true, servers=172.17.0.2[9042]}, customStoreClassName=org.infinispan.persistence.cassandra.CassandraStore], async=AsyncStoreConfiguration [attributes=AsyncStoreConfiguration = [enabled=false, modificationQueueSize=1024, threadPoolSize=1]], singletonStore=SingletonStoreConfiguration [attributes=SingletonStoreConfiguration = [enabled=false, push-state-timeout=10000, push-state-when-coordinator=true]]] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10137) Component dependency injection should not use reflection

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10137?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10137: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6948 > Component dependency injection should not use reflection > -------------------------------------------------------- > > Key: ISPN-10137 > URL: https://issues.jboss.org/browse/ISPN-10137 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4 > > > Quarkus allows reflection, but "[t]his is normally achieved by listing every class, method, field and constructor in a JSON file, and passing this as a parameter into the native image build", so it would be much better if we generated code to perform the injection without reflection. > Because the generated code needs to obey Java's accessibility rules and generating code in the same class is impractical, private fields and methods annotated {{@Inject}} will not be supported. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9027) Distinguishing multiple server Store configurations is impossible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Ryan Emerson reopened ISPN-9027: -------------------------------- > Distinguishing multiple server Store configurations is impossible > ----------------------------------------------------------------- > > Key: ISPN-9027 > URL: https://issues.jboss.org/browse/ISPN-9027 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 9.2.1.Final > Reporter: Sebastian Laskawiec > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > Attachments: clustered.xml > > > h3. Problem description > One of our users reported that when using two Deployed Cache Stores, their configuration gets overridden and both behaves as if they had the same configuration. Here's an example: > {code} > <distributed-cache name="cassandracache1" owners="2" segments="256" mode="SYNC"> > <store name="store1" class="org.infinispan.persistence.cassandra.CassandraStore" preload="true"> > <property name="autoCreateKeyspace"> > true > </property> > <property name="keyspace"> > Infinispan > </property> > <property name="entryTable"> > InfinispanEntries > </property> > <property name="servers"> > 172.17.0.2[9042] > </property> > </store> > </distributed-cache> > <distributed-cache name="cassandracache2" owners="2" segments="256" mode="SYNC"> > <store name="store2" class="org.infinispan.persistence.cassandra.CassandraStore" preload="true"> > <property name="autoCreateKeyspace"> > true > </property> > <property name="keyspace"> > Infinispan > </property> > <property name="entryTable"> > InfinispanEntries1 > </property> > <property name="servers"> > 172.17.0.2[9042] > </property> > </store> > </distributed-cache> > {code} > Both caches ({{cassandracache1}} and {{cassandracache2}}) use the same {{entryTable}} which is set to {{InfinispanEntries1}}. > h3. Investigation > {{CacheStoreFactory}} implementation were created to fabricate Loader/Writer instance based on parsed configuration (via {{createInstance}} method). This method receives from {{PersistenceManagerImpl}} an instance of an {{AbstractStoreConfiguration}} (here's an example (1)) two times - once per each parsed configuration. The parsing part seems OK but we do not parse Cache Store Name, which makes differentiating both configuration impossible. > h3. Proposed fix > * Add {{name}} attribute to {{StoreConfiguration}}. > * Either add an explicit parameter to {{CacheStoreFactory#createInstance(StoreConfiguration cfg, String cacheStoreName)}} or scan for Cache Store name in both implementations ({{DeployedCacheStoreFactory}} and {{LocalClassLoaderCacheStoreFactory}}. > {code} > (1) AbstractStoreConfiguration [attributes=DeployedStoreConfiguration = [fetchPersistentState=false, purgeOnStartup=false, ignoreModifications=false, preload=true, shared=false, transactional=false, maxBatchSize=100, properties={keyspace=Infinispan, connectionPool.poolTimeoutMillis=5, entryTable=InfinispanEntries, connectionPool.idleTimeoutSeconds=120, connectionPool.heartbeatIntervalSeconds=30, autoCreateKeyspace=true, servers=172.17.0.2[9042]}, customStoreClassName=org.infinispan.persistence.cassandra.CassandraStore], async=AsyncStoreConfiguration [attributes=AsyncStoreConfiguration = [enabled=false, modificationQueueSize=1024, threadPoolSize=1]], singletonStore=SingletonStoreConfiguration [attributes=SingletonStoreConfiguration = [enabled=false, push-state-timeout=10000, push-state-when-coordinator=true]]] > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2019