[JBoss JIRA] (ISPN-10115) Missing persistence element when reading a template resource
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10115?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10115:
-----------------------------------
Fix Version/s: 9.4.17.Final
(was: 9.4.16.Final)
> Missing persistence element when reading a template resource
> ------------------------------------------------------------
>
> Key: ISPN-10115
> URL: https://issues.jboss.org/browse/ISPN-10115
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1, 9.4.17.Final
>
>
> When reading a template resource, e.g via.
> {code:java}
> /subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS/local-cache-configuration=my-template:read-resource
> {code}
> The following is thrown:
> {code:java}
> [standalone@localhost:9990 /] /subsystem=datagrid-infinispan/cache-container=local/configurations=CONFIGURATIONS/local-cache-configuration=my-template:read-resource
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"datagrid-infinispan\"),
> (\"cache-container\" => \"local\"),
> (\"configurations\" => \"CONFIGURATIONS\"),
> (\"local-cache-configuration\" => \"my-template\"),
> (\"persistence\" => \"PERSISTENCE\")
> ]' not found",
> "rolled-back" => true
> }
> {code}
> The problem is caused by the persistence=PERSISTENCE element not being created by the xml reader. This is now necessary as the aliases to the old store entries refer to {{persistence=PERSISTENCE/file-store}} etc, which is called during a read-resource operation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-8329) ClusterTopologyManagerTest.testAbruptLeaveAfterGetStatus2 random failures with scattered cache
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8329?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8329:
----------------------------------
Fix Version/s: 9.4.17.Final
(was: 9.4.16.Final)
> ClusterTopologyManagerTest.testAbruptLeaveAfterGetStatus2 random failures with scattered cache
> ----------------------------------------------------------------------------------------------
>
> Key: ISPN-8329
> URL: https://issues.jboss.org/browse/ISPN-8329
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Tristan Tarrant
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.CR1, 9.4.17.Final
>
>
> Error Message
> Timed out waiting for rebalancing to complete on node ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665, current topology is CacheTopology{id=8, rebalanceId=4, currentCH=PartitionerConsistentHash:ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665: 85]}, pendingCH=null, unionCH=null, phase=NO_REBALANCE, actualMembers=[ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665], persistentUUIDs=[63b3a997-f229-475b-a14c-9c892f608ba0]}. rebalanceInProgress=false, currentChIsBalanced=false
> Stacktrace
> java.lang.RuntimeException: Timed out waiting for rebalancing to complete on node ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665, current topology is CacheTopology{id=8, rebalanceId=4, currentCH=PartitionerConsistentHash:ScatteredConsistentHash{ns=256, rebalanced=false, owners = (1)[ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665: 85]}, pendingCH=null, unionCH=null, phase=NO_REBALANCE, actualMembers=[ClusterTopologyManagerTest[SCATTERED_SYNC, tx=false]-NodeB-47665], persistentUUIDs=[63b3a997-f229-475b-a14c-9c892f608ba0]}. rebalanceInProgress=false, currentChIsBalanced=false
> at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:386)
> at org.infinispan.statetransfer.ClusterTopologyManagerTest.testAbruptLeaveAfterGetStatus2(ClusterTopologyManagerTest.java:430)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ... Removed 16 stack frames
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10463) Server uses disabled features
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10463?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10463:
-----------------------------------
Fix Version/s: 10.0.0.CR1
(was: 10.0.0.Beta5)
> Server uses disabled features
> -----------------------------
>
> Key: ISPN-10463
> URL: https://issues.jboss.org/browse/ISPN-10463
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.CR1, 9.4.17.Final
>
>
> Some Infinispan features are disabled in the product, e.g. data segmentation.
> This is done with a file META-INF/infinispan-features.properties added by the productization script in infinispan-commons:
> org.infinispan.feature.data-segmentation=false
> The properties file is read and the feature is disabled in library mode, but somehow the server doesn't find the properties file and the feature is enabled.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10429:
-----------------------------------
Fix Version/s: 10.0.0.CR1
(was: 10.0.0.Beta5)
> Hot Rod client doesn't retry on socket timeout
> ----------------------------------------------
>
> Key: ISPN-10429
> URL: https://issues.jboss.org/browse/ISPN-10429
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10431) REST client
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10431?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10431:
-----------------------------------
Fix Version/s: 10.0.0.CR1
(was: 10.0.0.Beta5)
> REST client
> -----------
>
> Key: ISPN-10431
> URL: https://issues.jboss.org/browse/ISPN-10431
> Project: Infinispan
> Issue Type: Feature Request
> Components: REST
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> There are several places in Infinispan where we need a common HTTP client API:
> * CLI
> * REST loader
> * Testsuite
> Since the testsuite already has one based on AHC, it can be refactored and reused.
> In the future it can be enhanced with ISPN-5186
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10386) OSGi integration tests never run
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10386?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10386:
-----------------------------------
Fix Version/s: 10.0.0.CR1
(was: 10.0.0.Beta5)
> OSGi integration tests never run
> --------------------------------
>
> Key: ISPN-10386
> URL: https://issues.jboss.org/browse/ISPN-10386
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite - Core
> Affects Versions: 10.0.0.Beta3, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> When we started supporting JDK9, Karaf and Pax-Exam didn't support it yet, so we disabled the OSGi integration tests when running on JDK11.
> When we started building on JDK11 and only running the tests on JDK8 with the {{java8-test}} profile, we didn't update the {{integrationtests-osgi}} POM, so the tests stay disabled regardless of profile.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10379) JCache tck-runner test failures are ignored in Jenkins
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10379?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10379:
-----------------------------------
Fix Version/s: 10.0.0.CR1
(was: 10.0.0.Beta5)
> JCache tck-runner test failures are ignored in Jenkins
> ------------------------------------------------------
>
> Key: ISPN-10379
> URL: https://issues.jboss.org/browse/ISPN-10379
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite - Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.CR1
>
>
> This build has 0 failures in Jenkins, but the console log says otherwise:
> https://ci.infinispan.org/job/Infinispan/job/PR-7110/1/
> {noformat}
> [2019-07-02T18:45:17.550Z] 18:45:16.738 [INFO] --- maven-failsafe-plugin:3.0.0-M3:integration-test (tck-embedded) @ infinispan-jcache-tck-runner ---
> [2019-07-02T18:45:17.550Z] 18:45:16.750 [INFO] Failsafe report directory: /home/infinispan/workspace/Infinispan_PR-7110/jcache/tck-runner/target/failsafe-reports-embedded
> ...
> [2019-07-02T18:45:53.348Z] 18:45:53.137 [ERROR] CacheExpiryTest.invokeAllReadThroughEnabledGetOnNonExistentEntry:1202
> [2019-07-02T18:45:53.348Z] Expected: is <0>
> [2019-07-02T18:45:53.348Z] but: was <5>
> [2019-07-02T18:45:53.348Z] 18:45:53.137 [ERROR] CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry:1110
> [2019-07-02T18:45:53.348Z] Expected: is <0>
> [2019-07-02T18:45:53.348Z] but: was <1>
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [ERROR] CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess:688 expected:<2> but was:<3>
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [INFO]
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [ERROR] Tests run: 491, Failures: 3, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (ISPN-10463) Server uses disabled features
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10463?page=com.atlassian.jira.plugin... ]
Dan Berindei commented on ISPN-10463:
-------------------------------------
jboss-modules doesn't export the {{META-INF}} directory by default, so only the classloader of infinispan-commons has access to its {{META-INF/infinispan-features.properties}}. We could use {{DefaultFileLookup#getAsURLsFromClassLoader()}} to search for the file in multiple classloaders, including the infinispan-commons one, or we could explicitly import the {{META-INF}} directory in all modules. Unfortunately both options fail/require further intervention to accept features properties files from other module (except maybe core).
> Server uses disabled features
> -----------------------------
>
> Key: ISPN-10463
> URL: https://issues.jboss.org/browse/ISPN-10463
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta5, 9.4.16.Final
>
>
> Some Infinispan features are disabled in the product, e.g. data segmentation.
> This is done with a file META-INF/infinispan-features.properties added by the productization script in infinispan-commons:
> org.infinispan.feature.data-segmentation=false
> The properties file is read and the feature is disabled in library mode, but somehow the server doesn't find the properties file and the feature is enabled.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months