August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6938) Retry ClusteredGetCommand through OutdatedTopologyExceptions

by Radim Vansa (JIRA)

Radim Vansa created ISPN-6938: --------------------------------- Summary: Retry ClusteredGetCommand through OutdatedTopologyExceptions Key: ISPN-6938 URL: https://issues.jboss.org/browse/ISPN-6938 Project: Infinispan Issue Type: Enhancement Components: Core Reporter: Radim Vansa Assignee: Radim Vansa Nowadays most commands deal with topology change during command execution by throwing an OutdatedTopologyException and retry in StateTransferInterceptor. xDistributionInterceptors still contain legacy logic that does the retry only within the interceptor, therefore missing loading in persistence interceptors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6586) Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6586?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6586: ------------------------------ Component/s: Core > Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner > ------------------------------------------------------- > > Key: ISPN-6586 > URL: https://issues.jboss.org/browse/ISPN-6586 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > Currently the remote value is fetched to origin and the function runs locally. That's not aligned with the idea of replicating only the operations, and suboptimal if the entry is bigger || more complex to marshall than the function return value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6936) Propagate exceptions from functional invocation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6936?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6936: ------------------------------ Component/s: Core > Propagate exceptions from functional invocation > ----------------------------------------------- > > Key: ISPN-6936 > URL: https://issues.jboss.org/browse/ISPN-6936 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > When a function passed to functional API throws an exception, this should be rethrown on caller side without being wrapped into {{RemoteException}}s, and it should not be logged by Infinispan on the way to caller. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6935) Use Collection instead of Set

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6935?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6935: ------------------------------ Status: Open (was: New) > Use Collection instead of Set > ----------------------------- > > Key: ISPN-6935 > URL: https://issues.jboss.org/browse/ISPN-6935 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > Currently the xManyCommand commands hold the keys in a set internally. During marshalling and splitting the set (when the command goes remote), we use {{HashSet}}. However, this has drawbacks: > a) if the set passed to command uses different means of equality than {{Object.hashCode()}} and {{Object.equals()}} we may lose some keys in the derived set - we don't inject dataContainer's keyEquivalence to the commands > b) as these sets are usually just iterated through (contains() is rare) it's less effective to use complex data structures as {{HashSet}} - plain {{ArrayList}} is sufficient. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6935) Use Collection instead of Set

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6935?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6935: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4493 > Use Collection instead of Set > ----------------------------- > > Key: ISPN-6935 > URL: https://issues.jboss.org/browse/ISPN-6935 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > Currently the xManyCommand commands hold the keys in a set internally. During marshalling and splitting the set (when the command goes remote), we use {{HashSet}}. However, this has drawbacks: > a) if the set passed to command uses different means of equality than {{Object.hashCode()}} and {{Object.equals()}} we may lose some keys in the derived set - we don't inject dataContainer's keyEquivalence to the commands > b) as these sets are usually just iterated through (contains() is rare) it's less effective to use complex data structures as {{HashSet}} - plain {{ArrayList}} is sufficient. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6586) Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6586?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6586: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4493 > Run ReadOnlyKeyCommand and ReadOnlyManyCommand on owner > ------------------------------------------------------- > > Key: ISPN-6586 > URL: https://issues.jboss.org/browse/ISPN-6586 > Project: Infinispan > Issue Type: Sub-task > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > Currently the remote value is fetched to origin and the function runs locally. That's not aligned with the idea of replicating only the operations, and suboptimal if the entry is bigger || more complex to marshall than the function return value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6936) Propagate exceptions from functional invocation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6936?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6936: ------------------------------ Status: Open (was: New) > Propagate exceptions from functional invocation > ----------------------------------------------- > > Key: ISPN-6936 > URL: https://issues.jboss.org/browse/ISPN-6936 > Project: Infinispan > Issue Type: Sub-task > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > When a function passed to functional API throws an exception, this should be rethrown on caller side without being wrapped into {{RemoteException}}s, and it should not be logged by Infinispan on the way to caller. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6936) Propagate exceptions from functional invocation

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6936?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6936: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4493 > Propagate exceptions from functional invocation > ----------------------------------------------- > > Key: ISPN-6936 > URL: https://issues.jboss.org/browse/ISPN-6936 > Project: Infinispan > Issue Type: Sub-task > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.0.0.Beta1 > > > When a function passed to functional API throws an exception, this should be rethrown on caller side without being wrapped into {{RemoteException}}s, and it should not be logged by Infinispan on the way to caller. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6650) org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent fails on Windows

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6650?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec resolved ISPN-6650. --------------------------------------- Fix Version/s: 9.0.0.Alpha4 Resolution: Cannot Reproduce Bug > org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent fails on Windows > ------------------------------------------------------------------------------------ > > Key: ISPN-6650 > URL: https://issues.jboss.org/browse/ISPN-6650 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Anna Manukyan > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.Alpha4 > > > The {{org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent}} tests are failing on Windows with the following exception: > {code} > java.lang.IllegalStateException: No caches registered! Use registerCacheManager(Cache... caches) to do that! > at org.infinispan.test.MultipleCacheManagersTest.clearContent(MultipleCacheManagersTest.java:98) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:786) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6650) org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent fails on Windows

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6650?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6650: -------------------------------------- Fix Version/s: 9.0.0.Beta1 9.0.0.Final (was: 9.0.0.Alpha4) > org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent fails on Windows > ------------------------------------------------------------------------------------ > > Key: ISPN-6650 > URL: https://issues.jboss.org/browse/ISPN-6650 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Anna Manukyan > Assignee: Sebastian Łaskawiec > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > The {{org.infinispan.server.hotrod.HotRodSingleClusteredTest.clearContent}} tests are failing on Windows with the following exception: > {code} > java.lang.IllegalStateException: No caches registered! Use registerCacheManager(Cache... caches) to do that! > at org.infinispan.test.MultipleCacheManagersTest.clearContent(MultipleCacheManagersTest.java:98) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:786) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016