May 2019 - infinispan-issues - Jboss List Archives

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

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9027: ------------------------------- Summary: Distinguishing multiple server Cache Store configurations is impossible (was: Distinguishing different Cache Store configurations is impossible) > Distinguishing multiple server Cache 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, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-51) ProtoSchemaBuilder fails on required property of type bytes

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-51?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-51: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > ProtoSchemaBuilder fails on required property of type bytes > ----------------------------------------------------------- > > Key: IPROTO-51 > URL: https://issues.jboss.org/browse/IPROTO-51 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 3.0.5.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Final, 4.1.5.Final, 4.3.0.Alpha3 > > > {code} > @ProtoField(number = 10, required = true) > public byte[] getName() { > return name; > } > {code} > reults in > Failure: org.infinispan.protostream.annotations.ProtoSchemaBuilderException: Repeated field 'name' of class app.model.Train cannot be marked required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-12) Add support for 'oneof' in generated proto schema

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-12?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-12: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > Add support for 'oneof' in generated proto schema > ------------------------------------------------- > > Key: IPROTO-12 > URL: https://issues.jboss.org/browse/IPROTO-12 > Project: Infinispan ProtoStream > Issue Type: Feature Request > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-62) Implement annotation based schema generation support for 'oneof'

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-62?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-62: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > Implement annotation based schema generation support for 'oneof' > ---------------------------------------------------------------- > > Key: IPROTO-62 > URL: https://issues.jboss.org/browse/IPROTO-62 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Final, 4.3.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-72) Integrate error-prone plugin in build system to catch more errors at compile time

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-72?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-72: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > Integrate error-prone plugin in build system to catch more errors at compile time > --------------------------------------------------------------------------------- > > Key: IPROTO-72 > URL: https://issues.jboss.org/browse/IPROTO-72 > Project: Infinispan ProtoStream > Issue Type: Task > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Final, 4.3.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-74) Allow repeatable fields to be written as a stream

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-74?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-74: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > Allow repeatable fields to be written as a stream > ------------------------------------------------- > > Key: IPROTO-74 > URL: https://issues.jboss.org/browse/IPROTO-74 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Reporter: Ryan Emerson > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha3 > > > Currently in order to write to a repeatable field it is necessary for an entire array or collection to be serialized at once. When writing larger collections it would be better if each object could be written individually from a stream. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-88) Replace usages of javassist.CtClass.toClass() with javassist.CtClass.toClass(java.lang.Class) for JDK 11 compatibility

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-88?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-88: -------------------------------- Fix Version/s: 4.3.0.Alpha3 (was: 4.3.0.Alpha1) > Replace usages of javassist.CtClass.toClass() with javassist.CtClass.toClass(java.lang.Class) for JDK 11 compatibility > ---------------------------------------------------------------------------------------------------------------------- > > Key: IPROTO-88 > URL: https://issues.jboss.org/browse/IPROTO-88 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha3 > > > The javadoc of javassist.CtClass.toClass() explains why. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9027) Distinguishing different Cache Store configurations is impossible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9027: ------------------------------- Component/s: Server > Distinguishing different Cache 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9027) Distinguishing different Cache Store configurations is impossible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9027: ------------------------------- Fix Version/s: 10.0.0.Beta4 9.4.14.Final > Distinguishing different Cache Store configurations is impossible > ----------------------------------------------------------------- > > Key: ISPN-9027 > URL: https://issues.jboss.org/browse/ISPN-9027 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9027) Distinguishing different Cache Store configurations is impossible

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9027?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9027: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6905 > Distinguishing different Cache Store configurations is impossible > ----------------------------------------------------------------- > > Key: ISPN-9027 > URL: https://issues.jboss.org/browse/ISPN-9027 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2019