March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11455) TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11455?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11455: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches > -------------------------------------------------------------------------- > > Key: ISPN-11455 > URL: https://issues.redhat.com/browse/ISPN-11455 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{TestingUtil.waitForNoRebalanceAcrossManagers()}} lookups all caches (including internal) to make sure no rebalance is in progress. > However, it is starting the internal caches while it isn't needed. It is the case for the counter's cache: > {noformat} > java.lang.RuntimeException: Cache org.infinispan.COUNTER timed out waiting for rebalancing to complete on node HotRodMergeTest-NodeA-42156, expected member list is [HotRodMergeTest-NodeA-42156, HotRodMergeTest-NodeB-64259], current member list is [HotRodMergeTest-NodeB-64259]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:429) > at org.infinispan.test.TestingUtil.waitForNoRebalanceAcrossManagers(TestingUtil.java:449) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterOverlappingMerge(HotRodMergeTest.java:114) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11367: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8031, https://github.com/infinispan/infinispan/pull/8036 (was: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8031) > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11456) ConfigurationUnitTest is fail on Windows

by 智博伊藤 (Jira)

智博伊藤 created ISPN-11456: ---------------------------- Summary: ConfigurationUnitTest is fail on Windows Key: ISPN-11456 URL: https://issues.redhat.com/browse/ISPN-11456 Project: Infinispan Issue Type: Bug Components: Core Reporter: 智博伊藤 ConfigurationUnitTest is fail on Windows as followings. mvn test -s maven-settings.xml -pl core -Dtest=org.infinispan.configuration.ConfigurationUnitTest -e [OK: 24, KO: 1, SKIP: 0] Test failed: org.infinispan.configuration.ConfigurationUnitTest.testSchema org.xml.sax.SAXParseException; systemId: file:/C:/Users/cito/develop/infinispan/core/target/classes/schema/infinispan-config-11.0.xsd; lineNumber: 1042; columnNumber: 93; cvc-datatype-valid.1.2.1: '${Transaction.auto-commit}' is not a valid value for 'boolean'. at java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204) at java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135) at java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4214) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(XSDHandler.java:4197) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.reportSchemaError(XSDAbstractTraverser.java:724) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAttributeTraverser.traverseLocal(XSDAttributeTraverser.java:179) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDAbstractTraverser.traverseAttrsAndAttrGrps(XSDAbstractTraverser.java:618) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.processComplexContent(XSDComplexTypeTraverser.java:1123) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseComplexTypeDecl(XSDComplexTypeTraverser.java:335) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDComplexTypeTraverser.traverseGlobal(XSDComplexTypeTraverser.java:191) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(XSDHandler.java:1459) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:644) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:617) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:576) at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:542) at java.xml/com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:276) at java.xml/javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:669) at java.xml/javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:701) at org.infinispan.configuration.ConfigurationUnitTest.testSchema(ConfigurationUnitTest.java:185) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124) at org.testng.internal.MethodInvocationHelper$1.runTestMethod(MethodInvocationHelper.java:230) at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24) at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:242) at org.testng.internal.Invoker.invokeMethod(Invoker.java:579) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.privateRun(TestRunner.java:648) at org.testng.TestRunner.run(TestRunner.java:505) at org.testng.SuiteRunner.runTest(SuiteRunner.java:455) at org.testng.SuiteRunner.access$000(SuiteRunner.java:40) at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:489) at org.testng.internal.thread.ThreadUtil$1.call(ThreadUtil.java:52) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) The cause is ${Transaction.auto-commit} does not replace to "true" in target/classes/schema/infinispan-config-11.0.xsd. <xs:attribute name="auto-commit" type="xs:boolean" default="${Transaction.auto-commit}"> In target/defaults.properties, the line above Transaction.auto-commit ends with\. This causes the Transaction.auto-commit line to be escaped. TakeOffline.min-wait=0 TemporaryGlobalStatePath.path=C:\Users\cito\AppData\Local\Temp\ Transaction.auto-commit=true Transaction.complete-timeout=60000 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11367: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8031 (was: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8034) > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11367: -------------------------------- Fix Version/s: 10.1.4.Final > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11367: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8034 (was: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8031) > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11367: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7974, https://github.com/infinispan/infinispan/pull/8031 (was: https://github.com/infinispan/infinispan/pull/7974) > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11455) TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11455?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11455: ------------------------------- Status: Open (was: New) > TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches > -------------------------------------------------------------------------- > > Key: ISPN-11455 > URL: https://issues.redhat.com/browse/ISPN-11455 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{TestingUtil.waitForNoRebalanceAcrossManagers()}} lookups all caches (including internal) to make sure no rebalance is in progress. > However, it is starting the internal caches while it isn't needed. It is the case for the counter's cache: > {noformat} > java.lang.RuntimeException: Cache org.infinispan.COUNTER timed out waiting for rebalancing to complete on node HotRodMergeTest-NodeA-42156, expected member list is [HotRodMergeTest-NodeA-42156, HotRodMergeTest-NodeB-64259], current member list is [HotRodMergeTest-NodeB-64259]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:429) > at org.infinispan.test.TestingUtil.waitForNoRebalanceAcrossManagers(TestingUtil.java:449) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterOverlappingMerge(HotRodMergeTest.java:114) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11455) TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11455?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11455: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8032, https://github.com/infinispan/infinispan/pull/8033 > TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches > -------------------------------------------------------------------------- > > Key: ISPN-11455 > URL: https://issues.redhat.com/browse/ISPN-11455 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{TestingUtil.waitForNoRebalanceAcrossManagers()}} lookups all caches (including internal) to make sure no rebalance is in progress. > However, it is starting the internal caches while it isn't needed. It is the case for the counter's cache: > {noformat} > java.lang.RuntimeException: Cache org.infinispan.COUNTER timed out waiting for rebalancing to complete on node HotRodMergeTest-NodeA-42156, expected member list is [HotRodMergeTest-NodeA-42156, HotRodMergeTest-NodeB-64259], current member list is [HotRodMergeTest-NodeB-64259]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:429) > at org.infinispan.test.TestingUtil.waitForNoRebalanceAcrossManagers(TestingUtil.java:449) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterOverlappingMerge(HotRodMergeTest.java:114) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11455) TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11455?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11455: ------------------------------- Summary: TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches (was: TestingUtil.waitForNoRebalanceAcrossManagers: skip create internal caches) > TestingUtil.waitForNoRebalanceAcrossManagers: do not start internal caches > -------------------------------------------------------------------------- > > Key: ISPN-11455 > URL: https://issues.redhat.com/browse/ISPN-11455 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > {{TestingUtil.waitForNoRebalanceAcrossManagers()}} lookups all caches (including internal) to make sure no rebalance is in progress. > However, it is starting the internal caches while it isn't needed. It is the case for the counter's cache: > {noformat} > java.lang.RuntimeException: Cache org.infinispan.COUNTER timed out waiting for rebalancing to complete on node HotRodMergeTest-NodeA-42156, expected member list is [HotRodMergeTest-NodeA-42156, HotRodMergeTest-NodeB-64259], current member list is [HotRodMergeTest-NodeB-64259]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:429) > at org.infinispan.test.TestingUtil.waitForNoRebalanceAcrossManagers(TestingUtil.java:449) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterOverlappingMerge(HotRodMergeTest.java:114) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020