March 2017 - infinispan-issues - Jboss List Archives

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6635?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6635: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Multi tenancy > ------------- > > Key: ISPN-6635 > URL: https://issues.jboss.org/browse/ISPN-6635 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.1.0.Final > > > Hosting Infinispan as a Service requires support of multi tenancy. > The design for this feature might be found here: https://github.com/infinispan/infinispan/wiki/Multi-tenancy-for-Hotrod-Se... > And implementation plan in the subtasks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6585) Persistence support in functional API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6585: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Persistence support in functional API > ------------------------------------- > > Key: ISPN-6585 > URL: https://issues.jboss.org/browse/ISPN-6585 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6479: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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.1.0.Final (was: 9.0.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.1.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6386) Remove max-entries from the documentation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6386?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6386: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Remove max-entries from the documentation > ----------------------------------------- > > Key: ISPN-6386 > URL: https://issues.jboss.org/browse/ISPN-6386 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Sebastian Łaskawiec > Assignee: Adrian Nistor > Fix For: 9.1.0.Final > > > In ISPN 9 we use size instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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.1.0.Final (was: 9.0.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.1.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6638) Implement multi-tenancy for Web Sockets

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6638?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6638: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Implement multi-tenancy for Web Sockets > --------------------------------------- > > Key: ISPN-6638 > URL: https://issues.jboss.org/browse/ISPN-6638 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.1.0.Final > > > Currently this implementation is out of scope. Please vote for it if you'd like it to be implemented. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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.1.0.Final (was: 9.0.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.1.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6448) ClassNotFoundException warnings in infinispan-rhq-plugin and infinispan-jcache-tck-runner build

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6448?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6448: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > ClassNotFoundException warnings in infinispan-rhq-plugin and infinispan-jcache-tck-runner build > ----------------------------------------------------------------------------------------------- > > Key: ISPN-6448 > URL: https://issues.jboss.org/browse/ISPN-6448 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Dan Berindei > Fix For: 9.1.0.Final > > > There are about 90 exceptions like this in total: > {noformat} > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] 6550 [WARN] ClassFinder: From jar path org/infinispan/objectfilter/impl/ProtobufMatcher$1.class could not load class org.infinispan.objectfilter.impl.ProtobufMatcher$1 > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] java.lang.ClassNotFoundException: org.infinispan.objectfilter.impl.ProtobufMatcher$1 > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.Class.forName0(Native Method) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.Class.forName(Class.java:348) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.Util.loadClassStrict(Util.java:171) ~[infinispan-commons.jar:9.0.0-SNAPSHOT] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.ClassFinder.findClassesOnPath(ClassFinder.java:145) [infinispan-commons.jar:9.0.0-SNAPSHOT] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.commons.util.ClassFinder.infinispanClasses(ClassFinder.java:90) [infinispan-commons.jar:9.0.0-SNAPSHOT] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.tools.rhq.RhqPluginXmlGenerator.getMBeanClasses(RhqPluginXmlGenerator.java:117) [infinispan-tools.jar:9.0.0-SNAPSHOT] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at org.infinispan.tools.rhq.RhqPluginXmlGenerator.start(RhqPluginXmlGenerator.java:75) [infinispan-tools.jar:9.0.0-SNAPSHOT] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:310) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:189) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:366) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.begin(Start.java:219) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Start.begin(Start.java:205) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Main.execute(Main.java:64) [tools.jar:?] > [13:09:19] : [org.infinispan:infinispan-jcache-tck-runner] at com.sun.tools.javadoc.Main.main(Main.java:54) [tools.jar:?] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6367) HotRod client unmarshalling ignores configured classloader

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6367?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6367: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > HotRod client unmarshalling ignores configured classloader > ---------------------------------------------------------- > > Key: ISPN-6367 > URL: https://issues.jboss.org/browse/ISPN-6367 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols, Server > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Fix For: 9.1.0.Final > > > The {{RemoteCacheManager}}'s {{ConfigurationBuilder}} allows you to set a classloader, but the client ignores that classloader when unmarshalling values received from the server. > This leads to problems when the client doesn't have a flat classpath (e.g. in an OSGi or JBoss Modules-based container). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017