July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6155) Drop the RHQ plugin

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6155?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6155: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Drop the RHQ plugin > ------------------- > > Key: ISPN-6155 > URL: https://issues.jboss.org/browse/ISPN-6155 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6154) Move GridFS to its own repository

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6154?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6154: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Move GridFS to its own repository > --------------------------------- > > Key: ISPN-6154 > URL: https://issues.jboss.org/browse/ISPN-6154 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6153) Move demos to their own source repository

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6153?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6153: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Move demos to their own source repository > ----------------------------------------- > > Key: ISPN-6153 > URL: https://issues.jboss.org/browse/ISPN-6153 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6103) LocalKeyAffinityTest.testFilteredRemoveServers random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6103?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6103: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > LocalKeyAffinityTest.testFilteredRemoveServers random failures > -------------------------------------------------------------- > > Key: ISPN-6103 > URL: https://issues.jboss.org/browse/ISPN-6103 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > {noformat} > 19:04:00,884 ERROR (testng-LocalKeyAffinityServiceTest:) [UnitTestTestNGListener] Test testFilteredRemoveServers(org.infinispan.affinity.impl.LocalKeyAffinityServiceTest) failed. > java.lang.AssertionError: > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?] > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.8.8.jar:?] > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:109) ~[test-classes/:?] > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:91) ~[test-classes/:?] > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:67) ~[test-classes/:?] > at org.infinispan.affinity.impl.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:77) ~[test-classes/:?] > at org.infinispan.affinity.impl.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:86) ~[test-classes/:?] > at org.infinispan.affinity.impl.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:60) ~[test-classes/:?] > at org.infinispan.affinity.impl.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:47) ~[test-classes/:?] > {noformat} > Counting the number of generated keys in the log, it seems to be correct, need better logging to determine if there are too few or too many keys in the queue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6094: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Use security actions to read system properties for configuration > ---------------------------------------------------------------- > > Key: ISPN-6094 > URL: https://issues.jboss.org/browse/ISPN-6094 > Project: Infinispan > Issue Type: Task > Components: Core, Embedded Querying > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Final > > > Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute: > * infinispan.arrays.debug > * infinispan.unsafe.force_multicast > * infinispan.compat (obsolete?) > * infinispan.debugDependencies > * infinispan.stagger.delay (introduced with ISPN-825) > * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE > We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6084) Continuous query should reject queries with orderBy

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6084?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6084: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Continuous query should reject queries with orderBy > --------------------------------------------------- > > Key: ISPN-6084 > URL: https://issues.jboss.org/browse/ISPN-6084 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.2.0.Final > > > Current behaviour it that orderBy is silently ignored. Disallowing this and throwing an exception would be preferable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6041) Remote Listeners: Client event reader thread reports EOF as error

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6041?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6041: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Remote Listeners: Client event reader thread reports EOF as error > ----------------------------------------------------------------- > > Key: ISPN-6041 > URL: https://issues.jboss.org/browse/ISPN-6041 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 9.2.0.Final > > > {noformat} > 14:02:14,904 ERROR (Client-Listener-87aa07aee56d43e1) [ClientListenerNotifier] ISPN004043: Unrecoverable error reading event from server /127.0.0.1:15530, exiting event reader thread > org.infinispan.client.hotrod.exceptions.TransportException: End of stream reached! > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:198) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:305) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readEvent(Codec20.java:147) > at org.infinispan.client.hotrod.event.ClientListenerNotifier$EventDispatcher.run(ClientListenerNotifier.java:252) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6477) Security tests always log a warning during cache manager shutdown

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6477?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6477: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Security tests always log a warning during cache manager shutdown > ----------------------------------------------------------------- > > Key: ISPN-6477 > URL: https://issues.jboss.org/browse/ISPN-6477 > Project: Infinispan > Issue Type: Bug > Components: Security, Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Alpha1, 9.2.0.Final > > > The problem is that {{TestingUtil.killCacheManagers()}} first stops each cache explicitly, and then {{DefaultCacheManager.stop()}} fails because it can't access the global ACL cache to perform a security check: > {noformat} > 17:07:00,613 WARN (testng-ExecutionAuthorizationTest:[]) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@4e83a98@Address:ExecutionAuthorizationTest-NodeB-14717 > org.infinispan.IllegalLifecycleStateException: ISPN000323: ___acl_cache is in 'TERMINATED' state and so it does not accept new invocations. Either restart it or recreate the cache container. > at org.infinispan.cache.impl.SimpleCacheImpl.getDataContainer(SimpleCacheImpl.java:1044) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsentInternal(SimpleCacheImpl.java:1116) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.StatsCollectingCache.computeIfAbsentInternal(StatsCollectingCache.java:270) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.cache.impl.SimpleCacheImpl.computeIfAbsent(SimpleCacheImpl.java:1111) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkSubjectPermissionAndRole(AuthorizationHelper.java:107) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:42) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.security.impl.SecureCacheImpl.getComponentRegistry(SecureCacheImpl.java:336) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.unregisterCacheMBean(DefaultCacheManager.java:714) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:671) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:708) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:688) ~[infinispan-core.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:673) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:656) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:652) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > at org.infinispan.test.MultipleCacheManagersTest.destroy(MultipleCacheManagersTest.java:87) [infinispan-core-tests.jar:9.0.0-SNAPSHOT] > {noformat} > {{DefaultCacheManager.stop()}} could check a cache's status before trying to unregister it from JMX, avoiding the security check when the cache is already {{TERMINATED}}. > {{DefaultCacheManager.unregisterCacheMBean()}} could also extract the cache's component registry from the global component registry and avoid the security check, since {{DefaultCacheManager.stop()}} already performed a security check. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6476: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > Integration test modules shouldn't change the failsafe plugin's lifecycle > ------------------------------------------------------------------------- > > Key: ISPN-6476 > URL: https://issues.jboss.org/browse/ISPN-6476 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Fix For: 9.2.0.Final > > > Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases. > On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6470) CapacityFactorsFunctionalTest.testCapacityFactors random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6470: ---------------------------------- Fix Version/s: 9.2.0.Final (was: 9.1.0.Final) > CapacityFactorsFunctionalTest.testCapacityFactors random failures > ------------------------------------------------------------------ > > Key: ISPN-6470 > URL: https://issues.jboss.org/browse/ISPN-6470 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > When nodes have different capacity factors, {{SyncConsistentHashFactory}} sometimes has trouble assigning the segments correctly: > {noformat} > java.lang.AssertionError: Expected between:<20.0> and:<50.0> but was:<52.0> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.infinispan.test.TestingUtil.assertBetween(TestingUtil.java:1455) > at org.infinispan.distribution.ch.CapacityFactorsFunctionalTest.assertOwned(CapacityFactorsFunctionalTest.java:96) > at org.infinispan.distribution.ch.CapacityFactorsFunctionalTest.testCapacityFactors(CapacityFactorsFunctionalTest.java:65) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017