January 2017 - infinispan-issues - Jboss List Archives

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6448?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6448: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6470?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6470: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6476: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6478) Netty worker thread starvation with events

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6478?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6478: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > Netty worker thread starvation with events > ------------------------------------------ > > Key: ISPN-6478 > URL: https://issues.jboss.org/browse/ISPN-6478 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 9.0.0.Beta3, 9.0.0.Final > > > As a result of ISPN-6005, we decoupled the incoming Hot Rod server invocations from sending events by adding a intermediate queue that maintains the events to send to clients. However, this separation can lead to a Netty worker thread starvation issue since we add the events to the queue in Netty's IO thread, so if the queue is full, incoming requests are stuck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6479: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6585?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6585: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6635) Multi tenancy

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6635?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6635: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6638?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6638: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > 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.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6639) Implement multi-tenancy for Memcached

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6639: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > Implement multi-tenancy for Memcached > ------------------------------------- > > Key: ISPN-6639 > URL: https://issues.jboss.org/browse/ISPN-6639 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Priority: Optional > Fix For: 9.0.0.Beta3 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6688) PreferAvailabilityStrategy: Improve selection of segment owners after merge

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6688?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6688: ----------------------------------- Fix Version/s: 9.0.0.Beta3 (was: 9.0.0.Beta2) > PreferAvailabilityStrategy: Improve selection of segment owners after merge > --------------------------------------------------------------------------- > > Key: ISPN-6688 > URL: https://issues.jboss.org/browse/ISPN-6688 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta3, 9.0.0.Final > > > {{PreferAvailabilityStrategy}} picks a winning CH after merge, but that CH is very likely to be the wrong one. We should improve our odds at preserving cache data by mixing CHs, and keeping from each node's response only the information about the segments it owns itself. > The downside is that {{PreferAvailabilityStrategy}} becomes tightly coupled with {{DefaultConsistentHash}}/{{ReplicatedConsistentHash}}, and users that want to add custom {{ConsistentHash}} implementations will have to re-implement {{PreferAvailabilityStrategy}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017