February 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9957) InfinisapnSubsystemXMLReader ignores configuration attribute on local-cache elements

by Oliver Lüttin (Jira)

Oliver Lüttin created ISPN-9957: ----------------------------------- Summary: InfinisapnSubsystemXMLReader ignores configuration attribute on local-cache elements Key: ISPN-9957 URL: https://issues.jboss.org/browse/ISPN-9957 Project: Infinispan Issue Type: Bug Components: Integration Affects Versions: 9.4.6.Final, 9.4.5.Final, 9.4.4.Final Reporter: Oliver Lüttin Attachments: example.cli InfinisapnSubsystemXMLReader ignores configuration attribute on local-cache elements. The method {code:java} initPersistenceConfiguration(cacheConfigurationAddress, additionalConfigurationOperations); {code} , which is called from parseLocalCache, adds an entry to additionalConfigurationOperations. This causes the method {code:java} addCacheConfiguration(String cacheType, PathAddress containerAddress, Map<PathAddress, ModelNode> operations, boolean configurationOnly, ModelNode cacheConfiguration, Map<PathAddress, ModelNode> additionalConfigurationOperations, PathAddress cacheConfigurationAddress) {code} to call {code:java} addCacheConfiguration(String cacheType, PathAddress containerAddress, Map<PathAddress, ModelNode> operations, boolean configurationOnly, ModelNode cacheConfiguration, Map<PathAddress, ModelNode> additionalConfigurationOperations, PathAddress cacheConfigurationAddress) {code} without a configurationName. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9956) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

Vladimir Blagojevic created ISPN-9956: ----------------------------------------- Summary: Admin console - clusters link does not work in standalone mode Key: ISPN-9956 URL: https://issues.jboss.org/browse/ISPN-9956 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 10.0.0.Alpha3, 9.4.6.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-9955: ----------------------------------------- Assignee: Vladimir Blagojevic > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9955: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/276 > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9955: -------------------------------------- Status: Open (was: New) > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9955: -------------------------------------- Description: Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. (was: Clusters link does not work in standalone mode. ) > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. Clicking on default link in the attached screenshot does not work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9955: -------------------------------------- Attachment: Screen Shot 2019-02-08 at 8.52.50 AM.png > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-9955?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-9955: -------------------------------------- Description: Clusters link does not work in standalone mode. > Admin console - clusters link does not work in standalone mode > -------------------------------------------------------------- > > Key: ISPN-9955 > URL: https://issues.jboss.org/browse/ISPN-9955 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Vladimir Blagojevic > Priority: Major > Attachments: Screen Shot 2019-02-08 at 8.52.50 AM.png > > > Clusters link does not work in standalone mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9954) Missing dependency on server/integration/testsuite

by Gustavo Lira (Jira)

[ https://issues.jboss.org/browse/ISPN-9954?page=com.atlassian.jira.plugin.... ] Gustavo Lira updated ISPN-9954: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6671 > Missing dependency on server/integration/testsuite > -------------------------------------------------- > > Key: ISPN-9954 > URL: https://issues.jboss.org/browse/ISPN-9954 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.6.Final > Reporter: Gustavo Lira > Assignee: Gustavo Lira > Priority: Major > > infinispan-remote dependecy is missing when we try to build infinispan using the following command > {code}mvn -s settings_mead_jdg.xml -f infinispan/pom.xml -pl server/integration/testsuite -B clean verify -Dmaven.test.failure.ignore=true -Pclient.hotrod.osgi -Dversion.karaf=4.2.0 -Dzip.dist=/path/to/infinispan-server.zip {code} > Here the throwed exception > {noformat} > [INFO] Running org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT > [OK: 0, KO: 0, SKIP: 0] Test starting: RemoteCacheOsgiIT.initializationError > [OK: 0, KO: 1, SKIP: 0] Test failed: RemoteCacheOsgiIT.initializationError > org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project? > at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:195) > at org.ops4j.pax.exam.junit.impl.ProbeRunner.<init>(ProbeRunner.java:78) > at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82) > at org.ops4j.pax.exam.junit.PaxExam.<init>(PaxExam.java:73) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104) > at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86) > at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) > at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) > at org.junit.runner.Computer.getRunner(Computer.java:40) > at org.junit.runner.Computer$1.runnerForClass(Computer.java:31) > at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) > at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101) > at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87) > at org.junit.runners.Suite.<init>(Suite.java:81) > at org.junit.runner.Computer.getSuite(Computer.java:28) > at org.junit.runner.Request.classes(Request.java:75) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:126) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) > Caused by: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project? > at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(MavenUtils.java:75) > at org.ops4j.pax.exam.MavenUtils$1.getVersion(MavenUtils.java:109) > at org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(MavenArtifactUrlReference.java:86) > at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:90) > at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248) > at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184) > ... 28 more > 07:31:08.257 [main] ERROR org.infinispan.commons.test.TestSuiteProgress - Test failed: RemoteCacheOsgiIT.initializationError > org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project? > at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:195) ~[pax-exam-spi-4.11.0.jar:?] > at org.ops4j.pax.exam.junit.impl.ProbeRunner.<init>(ProbeRunner.java:78) ~[pax-exam-junit4-4.11.0.jar:?] > at org.ops4j.pax.exam.junit.PaxExam.createDelegate(PaxExam.java:82) ~[pax-exam-junit4-4.11.0.jar:?] > at org.ops4j.pax.exam.junit.PaxExam.<init>(PaxExam.java:73) ~[pax-exam-junit4-4.11.0.jar:?] > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_191] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_191] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_191] > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_191] > at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runner.Computer.getRunner(Computer.java:40) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runner.Computer$1.runnerForClass(Computer.java:31) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:101) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runners.model.RunnerBuilder.runners(RunnerBuilder.java:87) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runners.Suite.<init>(Suite.java:81) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runner.Computer.getSuite(Computer.java:28) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.junit.runner.Request.classes(Request.java:75) ~[junit-4.12.0.redhat-003.jar:4.12.0.redhat-003] > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:126) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) [surefire-junit47-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) [surefire-booter-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) [surefire-booter-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) [surefire-booter-3.0.0-M1.jar:3.0.0-M1] > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) [surefire-booter-3.0.0-M1.jar:3.0.0-M1] > Caused by: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project? > at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(MavenUtils.java:75) ~[pax-exam-4.11.0.jar:?] > at org.ops4j.pax.exam.MavenUtils$1.getVersion(MavenUtils.java:109) ~[pax-exam-4.11.0.jar:?] > at org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(MavenArtifactUrlReference.java:86) ~[pax-exam-4.11.0.jar:?] > at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:90) ~[pax-exam-4.11.0.jar:?] > at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83) ~[test-classes/:?] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_191] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_191] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_191] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_191] > at org.ops4j.pax.exam.spi.reactors.ReactorManager.addConfigurationsToReactor(ReactorManager.java:248) ~[pax-exam-spi-4.11.0.jar:?] > at org.ops4j.pax.exam.spi.reactors.ReactorManager.prepareReactor(ReactorManager.java:184) ~[pax-exam-spi-4.11.0.jar:?] > ... 28 more > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.037 s <<< FAILURE! - in org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT > [ERROR] initializationError(org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT) Time elapsed: 0.008 s <<< ERROR! > org.ops4j.pax.exam.TestContainerException: java.lang.IllegalArgumentException: Could not resolve version. Do you have a dependency for org.infinispan/infinispan-remote in your maven project? > at org.infinispan.server.test.client.hotrod.osgi.RemoteCacheOsgiIT.config(RemoteCacheOsgiIT.java:83) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9955) Admin console - clusters link does not work in standalone mode

by Vladimir Blagojevic (Jira)

Vladimir Blagojevic created ISPN-9955: ----------------------------------------- Summary: Admin console - clusters link does not work in standalone mode Key: ISPN-9955 URL: https://issues.jboss.org/browse/ISPN-9955 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.4.6.Final, 10.0.0.Alpha3 Reporter: Vladimir Blagojevic -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2019