[JBoss JIRA] (ISPN-9835) Jenkinsfile snapshot deployment fails
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9835?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9835:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Jenkinsfile snapshot deployment fails
> -------------------------------------
>
> Key: ISPN-9835
> URL: https://issues.jboss.org/browse/ISPN-9835
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 10.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> {noformat}
> 11:16:21.413 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact
> {noformat}
> https://ci.infinispan.org/job/Infinispan/job/master/1005
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9921) Warning instead if exception with 0 capacity node and clustered locks
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9921?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9921:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.4.7.Final
Resolution: Done
> Warning instead if exception with 0 capacity node and clustered locks
> ---------------------------------------------------------------------
>
> Key: ISPN-9921
> URL: https://issues.jboss.org/browse/ISPN-9921
> Project: Infinispan
> Issue Type: Enhancement
> Components: Clustered Locks
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.7.Final
>
>
> If we don't specify a number of owners for the locks and the node is a zero capacity node, the actual implementation raises an error, which is not the case when replicated caches are created by the user in this scenario.
> Log a warning message instead of an exception for this case and eventually the same warning when the user defines replicated caches and the node is configured as a zero-capacity node
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9962) Feature-packs should optionally depend on jdk-unsupported and sun.jdk
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9962?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9962:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Feature-packs should optionally depend on jdk-unsupported and sun.jdk
> ---------------------------------------------------------------------
>
> Key: ISPN-9962
> URL: https://issues.jboss.org/browse/ISPN-9962
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.7.Final
>
>
> Currently our feature-packs depend on both "sun.jdk" and "jdk.unsupported" in an inconsistent manner. For the latest versions of Wildfly, we need to use the latter, whilst for older ones we need to use the former. Therefore, for all modules that require access to unsupported classes, we must provide an optional dependency on both of the above modules.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of Wildfly
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9964:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Logging incompatibility when deploying modules on older versions of Wildfly
> ---------------------------------------------------------------------------
>
> Key: ISPN-9964
> URL: https://issues.jboss.org/browse/ISPN-9964
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ISPN-9954) Missing dependency on server/integration/testsuite
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9954?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9954:
----------------------------------
Status: Pull Request Sent (was: Reopened)
> Missing dependency on server/integration/testsuite
> --------------------------------------------------
>
> Key: ISPN-9954
> URL: https://issues.jboss.org/browse/ISPN-9954
> Project: Infinispan
> Issue Type: Bug
> Components: Dependency, Test Suite - Server
> Affects Versions: 9.4.6.Final
> Reporter: Gustavo Lira
> Assignee: Gustavo Lira
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.7.Final
>
>
> 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
[JBoss JIRA] (ISPN-9968) JCacheStateAwarenessIT failure due to infinispan-remote dependency
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9968?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9968:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> JCacheStateAwarenessIT failure due to infinispan-remote dependency
> ------------------------------------------------------------------
>
> Key: ISPN-9968
> URL: https://issues.jboss.org/browse/ISPN-9968
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Beta1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta1, 9.4.7.Final
>
>
> ISPN-9554 introduced a dependency on {{infinispan-remote}} on the server/integration/testsuite that results in classes not being loaded as expected. We should remove this dependency and find an alternative solution for ISPN-9554.
> JCacheStateAwarenessIT failure cause:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Logger implementation class org.infinispan.jcache.logging.Log_$logger has no matching constructor
> at org.jboss.logging.Logger$1.run(Logger.java:2562) ~[?:?]
> at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2529) ~[?:?]
> at org.jboss.logging.Logger.getMessageLogger(Logger.java:2516) ~[?:?]
> at org.infinispan.commons.logging.LogFactory.getLog(LogFactory.java:18) ~[?:?]
> at org.infinispan.jcache.AbstractJCachingProvider.<clinit>(AbstractJCachingProvider.java:23) ~[?:?]
> 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 java.lang.Class.newInstance(Class.java:442) ~[?:?]
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) ~[?:?]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month