November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10911) HotRodMultiMapOperations random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10911?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10911: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > HotRodMultiMapOperations random failures > ---------------------------------------- > > Key: ISPN-10911 > URL: https://issues.jboss.org/browse/ISPN-10911 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.1.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Beta1 > > > Multimap operations are asynchronous, and the test doesn't wait for the writes to finish before starting a get. Multimap and Infinispan in general do not guarantee that asynchronous operations started from the same thread run in any particular order. > {noformat} > 09:07:49,325 ERROR (testng-HotRodMultiMapOperations:[]) [TestSuiteProgress] Test failed: HotRodMultiMapOperations.testMultiMap > java.lang.AssertionError: expected:<2> but was:<0> > at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12] > at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:645) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:631) ~[junit-4.12.jar:4.12] > at org.infinispan.server.functional.HotRodMultiMapOperations.testMultiMap(HotRodMultiMapOperations.java:41) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10912) HotRod server retries CheckAddressTask indefinitely during shutdown

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10912?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10912: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > HotRod server retries CheckAddressTask indefinitely during shutdown > ------------------------------------------------------------------- > > Key: ISPN-10912 > URL: https://issues.jboss.org/browse/ISPN-10912 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.1.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > Normally retrying to add the local address to the topology cache is a good idea, but {{IllegalLifecycleStateException}} should be handled differently. > {noformat} > 09:09:03,471 DEBUG (remote-thread--p11-t2:[]) [HotRodServer] Error re-adding address to topology cache, retrying > org.infinispan.commons.CacheException: org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. > at org.infinispan.server.hotrod.HotRodServer$ReAddMyAddressListener.lambda$recursionTopologyChanged$0(HotRodServer.java:678) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$submitConsumer$3(LocalClusterExecutor.java:78) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859) ~[?:?] > at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837) ~[?:?] > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[?:?] > at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) ~[?:?] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$localInvocation$6(LocalClusterExecutor.java:97) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:215) [infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] > at java.lang.Thread.run(Thread.java:834) [?:?] > Caused by: org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. > at org.infinispan.manager.DefaultCacheManager.assertIsNotTerminated(DefaultCacheManager.java:1070) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:502) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:196) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.UnwrappingEmbeddedCacheManager.getCache(UnwrappingEmbeddedCacheManager.java:25) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.server.hotrod.CheckAddressTask.apply(HotRodServer.java:725) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.server.hotrod.CheckAddressTask.apply(HotRodServer.java:712) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$localInvocation$6(LocalClusterExecutor.java:94) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > ... 4 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10913) Exclude checker-qual from caffeine dependency

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10913?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10913: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Exclude checker-qual from caffeine dependency > --------------------------------------------- > > Key: ISPN-10913 > URL: https://issues.jboss.org/browse/ISPN-10913 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.0.Beta1 > > > {noformat} > checker-qual And errorprone are annotations which Java doesn’t require at runtime unless you reflectively load them when inspecting the methods. Unfortunately other languages will not classload without them, making them required. You can exclude safely in Java. > {noformat} > src: https://github.com/ben-manes/caffeine/issues/300#issuecomment-507292996 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10871) Add org.aesh:readline to dependency management

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10871?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10871: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Add org.aesh:readline to dependency management > ---------------------------------------------- > > Key: ISPN-10871 > URL: https://issues.jboss.org/browse/ISPN-10871 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.0.Beta1 > > > Add the {{org.aesh:readline}} to the dependency management so its version can be overwritten downstream. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10880) JCacheConfigurationTest leaks cache manager

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10880?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10880: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > JCacheConfigurationTest leaks cache manager > ------------------------------------------- > > Key: ISPN-10880 > URL: https://issues.jboss.org/browse/ISPN-10880 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 10.0.0.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Beta1 > > > {noformat} > ThreadLeakCheckerorg.infinispan.commons.test.ThreadLeakChecker$LeakException: Leaked thread: expiration-thread--p446-t1 << testng-JCacheConfigurationTest << org.infinispan.jcache.JCacheConfigurationTest > ... > Caused by: org.infinispan.commons.test.ThreadLeakChecker$LeakException: testng-JCacheConfigurationTest << org.infinispan.jcache.JCacheConfigurationTest > at org.infinispan.commons.test.ThreadLeakChecker$ThreadInfoLocal.childValue(ThreadLeakChecker.java:107) > ... > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:713) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:391) > at org.infinispan.jcache.embedded.JCacheManager.<init>(JCacheManager.java:75) > at org.infinispan.jcache.JCacheConfigurationTest.lambda$testJCacheManagerWithRealJarFileSchema$1(JCacheConfigurationTest.java:107) > at org.infinispan.jcache.util.JCacheTestingUtil.withCachingProvider(JCacheTestingUtil.java:36) > at org.infinispan.jcache.JCacheConfigurationTest.testJCacheManagerWithRealJarFileSchema(JCacheConfigurationTest.java:104) > {noformat} > The leak is only reported some of the time because {{AbstractJCacheManager}} has a {{finalize()}} method and stops the underlying cache manager. > The threads created by {{DefaultCacheManager}} ensure it's still referenced during finalization, allowing it to stop cleanly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10881?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10881: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains > ---------------------------------------------------------------- > > Key: ISPN-10881 > URL: https://issues.jboss.org/browse/ISPN-10881 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 10.0.0.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Final > > > {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name. > Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10885) REST Reindex action

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10885?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10885: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > REST Reindex action > ------------------- > > Key: ISPN-10885 > URL: https://issues.jboss.org/browse/ISPN-10885 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying, REST > Affects Versions: 10.0.1.Final > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Final > > > The Cache rest resource should implement a /rest/v2/caches/{cacheName}?action=reindex&mode=[sync|async] > The method should return a 200 OK for sync and 202 Accepted for async reindex. It should also not initiate a new reindexing if one is running already and return 409 Conflict. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10888) Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10888?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10888: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided > ------------------------------------------------------------------------------------------- > > Key: ISPN-10888 > URL: https://issues.jboss.org/browse/ISPN-10888 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache. > In these cases do not add both, just one. > Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _' -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10891) JGroupsTransport registers the channel in JMX ignoring the cacheManagerName

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10891?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10891: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > JGroupsTransport registers the channel in JMX ignoring the cacheManagerName > --------------------------------------------------------------------------- > > Key: ISPN-10891 > URL: https://issues.jboss.org/browse/ISPN-10891 > Project: Infinispan > Issue Type: Bug > Components: Core, JMX, reporting and management > Affects Versions: 9.4.16.Final, 10.0.1.Final > Reporter: dan.berindei > Priority: Major > > {{JGroupsTransport}} registers the JGroups channel in JMX with a name like {{<jmx-domain>:type=channel,cluster={{cluster-name>}}. > If two managers have a different {{cacheManagerName}}, all the cache manager and cache components can be registered along each other in the same JMX domain. The channel object name however doesn't include the manager name, so the 2nd cache manager fails to register its channel, and because of JGRP-2393 the cause of the error is hidden. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10905) Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client)

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10905?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10905: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Hot Rod client should not use JmxUtil (no PrivilegedActions needed by client) > ----------------------------------------------------------------------------- > > Key: ISPN-10905 > URL: https://issues.jboss.org/browse/ISPN-10905 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Remote Protocols > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019