May 2019 - infinispan-issues - Jboss List Archives

[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 updated ISPN-9027: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6905, https://github.com/infinispan/infinispan/pull/6922, https://github.com/infinispan/infinispan/pull/6955, https://github.com/infinispan/infinispan/pull/6956 (was: https://github.com/infinispan/infinispan/pull/6905, https://github.com/infinispan/infinispan/pull/6922) > 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-9457) Async caches should provide a way to track replication time stats

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9457?page=com.atlassian.jira.plugin.... ] Ryan Emerson reopened ISPN-9457: -------------------------------- > 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 Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9457?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9457: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6907, https://github.com/infinispan/infinispan/pull/6927, https://github.com/infinispan/infinispan/pull/6955, https://github.com/infinispan/infinispan/pull/6956 (was: https://github.com/infinispan/infinispan/pull/6907, https://github.com/infinispan/infinispan/pull/6927) > 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-10223) As a developer, I need docs for using Maven, Gradle, and Ivy

by Donald Naro (Jira)

Donald Naro created ISPN-10223: ---------------------------------- Summary: As a developer, I need docs for using Maven, Gradle, and Ivy Key: ISPN-10223 URL: https://issues.jboss.org/browse/ISPN-10223 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Affects Versions: 10.0.0.Final Reporter: Donald Naro Assignee: Donald Naro Provide instructions for managing dependencies with maven, gradle, and ivy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10219) security session doc with wrong declarative configuration

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10219?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10219: -------------------------------- Fix Version/s: 10.0.0.Beta4 9.4.14.Final > security session doc with wrong declarative configuration > --------------------------------------------------------- > > Key: ISPN-10219 > URL: https://issues.jboss.org/browse/ISPN-10219 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core, Security > Affects Versions: 9.4.13.Final > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > Session 23.1.3. Embedded Configuration has some wrong declarative configurations. > The following declarative configuration has some errors: > {code:xml} > <cache-container default-cache="secured"> > <security> > <authorization enabled="true"> > <identity-role-mapper /> > <role name="admin" permissions="ALL" /> > <role name="reader" permissions="READ" /> > <role name="writer" permissions="WRITE" /> > <role name="supervisor" permissions="READ WRITE EXEC BULK" /> > </authorization> > </security> > <local-cache name="secured"> > <security> > <authorization roles="admin reader writer supervisor" /> > </security> > </local-cache> > </cache-container> > {code} > # name attribute is mandatory into cache-container > # 'enabled' isn't an allowed attribute for the 'authorization' element. The 'authorization' element doesn't allow any attributes > # There's no permission BULK > The XML should be like this: > {code:xml} > <cache-container name="secure" default-cache="secured"> > <security> > <authorization> > <identity-role-mapper /> > <role name="admin" permissions="ALL" /> > <role name="reader" permissions="READ" /> > <role name="writer" permissions="WRITE" /> > <role name="supervisor" permissions="READ WRITE EXEC" /> > </authorization> > </security> > <local-cache name="secured"> > <security> > <authorization roles="admin reader writer supervisor" /> > </security> > </local-cache> > </cache-container> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10222) (Prepare|Commit)Commands don't pay attention to flags on the Cache

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10222?page=com.atlassian.jira.plugin... ] Will Burns closed ISPN-10222. ----------------------------- Resolution: Rejected Note an issue, due to incorrect assertion. > (Prepare|Commit)Commands don't pay attention to flags on the Cache > ------------------------------------------------------------------ > > Key: ISPN-10222 > URL: https://issues.jboss.org/browse/ISPN-10222 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta3 > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > The prepare and commit commands dont' allow for passed flags like other commands. This means that a flag such as SKIP_CACHE_STORE will be ignore and an entry will always be written to the store. This is easily apparent when having preload with a tx cache as it will insert every single entry back into the store again! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10222) (Prepare|Commit)Commands don't pay attention to flags on the Cache

by Will Burns (Jira)

Will Burns created ISPN-10222: --------------------------------- Summary: (Prepare|Commit)Commands don't pay attention to flags on the Cache Key: ISPN-10222 URL: https://issues.jboss.org/browse/ISPN-10222 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.0.0.Beta3 Reporter: Will Burns Fix For: 10.0.0.Final The prepare and commit commands dont' allow for passed flags like other commands. This means that a flag such as SKIP_CACHE_STORE will be ignore and an entry will always be written to the store. This is easily apparent when having preload with a tx cache as it will insert every single entry back into the store again! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10221) Cannot start Infinispan Server when running on Windows

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10221?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10221: ----------------------------------- Fix Version/s: 10.0.0.Beta4 9.4.14.Final > Cannot start Infinispan Server when running on Windows > ------------------------------------------------------ > > Key: ISPN-10221 > URL: https://issues.jboss.org/browse/ISPN-10221 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Beta3 > Environment: win 08/12 - jdk8/jdk11 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 10.0.0.Beta4, 9.4.14.Final > > > The Infinispan server is not able to start when running on Windows. The workaround was add {{<env key="STANDALONE_CONF" value="notfound.bat"/>}} in server/integration/src/main/ant/infinispan-server.xml > {code:xml} > <env key="JAVA_OPTS" value="${server.jvm.args} -Djboss.socket.binding.port-offset=${port.offset} -Djboss.node.name=${jboss.node.name}"/> > <env key="JBOSS_HOME" value="${server.dist}"/> > <env key="JAVA" value="${server.jvm}/bin/java"/> > <env key="STANDALONE_CONF" value="notfound.bat"/> > </exec> > <echo>Waiting for Infinispan server to start</echo> > <waitfor maxwait="30" maxwaitunit="second" checkevery="1" checkeveryunit="second"> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10221) Cannot start Infinispan Server when running on Windows

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10221?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10221: ----------------------------------- Security: (was: Red Hat Internal) > Cannot start Infinispan Server when running on Windows > ------------------------------------------------------ > > Key: ISPN-10221 > URL: https://issues.jboss.org/browse/ISPN-10221 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Beta3 > Environment: win 08/12 - jdk8/jdk11 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > > The Infinispan server is not able to start when running on Windows. The workaround was add {{<env key="STANDALONE_CONF" value="notfound.bat"/>}} in server/integration/src/main/ant/infinispan-server.xml > {code:xml} > <env key="JAVA_OPTS" value="${server.jvm.args} -Djboss.socket.binding.port-offset=${port.offset} -Djboss.node.name=${jboss.node.name}"/> > <env key="JBOSS_HOME" value="${server.dist}"/> > <env key="JAVA" value="${server.jvm}/bin/java"/> > <env key="STANDALONE_CONF" value="notfound.bat"/> > </exec> > <echo>Waiting for Infinispan server to start</echo> > <waitfor maxwait="30" maxwaitunit="second" checkevery="1" checkeveryunit="second"> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10219) security session doc with wrong declarative configuration

by Gustavo Lira e Silva (Jira)

[ https://issues.jboss.org/browse/ISPN-10219?page=com.atlassian.jira.plugin... ] Gustavo Lira e Silva reassigned ISPN-10219: ------------------------------------------- Assignee: Gustavo Lira e Silva > security session doc with wrong declarative configuration > --------------------------------------------------------- > > Key: ISPN-10219 > URL: https://issues.jboss.org/browse/ISPN-10219 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core, Security > Affects Versions: 9.4.13.Final > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > > Session 23.1.3. Embedded Configuration has some wrong declarative configurations. > The following declarative configuration has some errors: > {code:xml} > <cache-container default-cache="secured"> > <security> > <authorization enabled="true"> > <identity-role-mapper /> > <role name="admin" permissions="ALL" /> > <role name="reader" permissions="READ" /> > <role name="writer" permissions="WRITE" /> > <role name="supervisor" permissions="READ WRITE EXEC BULK" /> > </authorization> > </security> > <local-cache name="secured"> > <security> > <authorization roles="admin reader writer supervisor" /> > </security> > </local-cache> > </cache-container> > {code} > # name attribute is mandatory into cache-container > # 'enabled' isn't an allowed attribute for the 'authorization' element. The 'authorization' element doesn't allow any attributes > # There's no permission BULK > The XML should be like this: > {code:xml} > <cache-container name="secure" default-cache="secured"> > <security> > <authorization> > <identity-role-mapper /> > <role name="admin" permissions="ALL" /> > <role name="reader" permissions="READ" /> > <role name="writer" permissions="WRITE" /> > <role name="supervisor" permissions="READ WRITE EXEC" /> > </authorization> > </security> > <local-cache name="secured"> > <security> > <authorization roles="admin reader writer supervisor" /> > </security> > </local-cache> > </cache-container> > {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