February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8820) Don't allow lower-bound equals to upper-bound

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8820?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8820: ------------------------------ Status: Open (was: New) > Don't allow lower-bound equals to upper-bound > --------------------------------------------- > > Key: ISPN-8820 > URL: https://issues.jboss.org/browse/ISPN-8820 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > The upper- and lower-bound are both inclusive. However, the case where upper==lower shouldn't be allowed since it can't change the counter's value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8839) ClusterTopologyManagerImplTest leaks threads

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8839?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8839: ------------------------------- Status: Open (was: New) > ClusterTopologyManagerImplTest leaks threads > -------------------------------------------- > > Key: ISPN-8839 > URL: https://issues.jboss.org/browse/ISPN-8839 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.2.0.CR3 > > > Both test methods create an {{ExecutorService}} but don't shut it down. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8839) ClusterTopologyManagerImplTest leaks threads

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8839?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8839: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5768 > ClusterTopologyManagerImplTest leaks threads > -------------------------------------------- > > Key: ISPN-8839 > URL: https://issues.jboss.org/browse/ISPN-8839 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.2.0.CR3 > > > Both test methods create an {{ExecutorService}} but don't shut it down. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7011: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5768 > @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode > ------------------------------------------------------------------------ > > Key: ISPN-7011 > URL: https://issues.jboss.org/browse/ISPN-7011 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation). > Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure: > {noformat} > java.lang.IllegalStateException: Two tests with the same name running in parallel: test > at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88) > at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115) > 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:498) > 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.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8478) Reduce build memory usage

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8478?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8478: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/5528, https://github.com/infinispan/infinispan/pull/5768 (was: https://github.com/infinispan/infinispan/pull/5528) > Reduce build memory usage > ------------------------- > > Key: ISPN-8478 > URL: https://issues.jboss.org/browse/ISPN-8478 > Project: Infinispan > Issue Type: Task > Components: Build > Affects Versions: 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.0.Beta1 > > > The CI Maven process runs without a max heap parameter, so it can use up to 1/4 of agent RAM. It should run with a specific limit and so should all the other JVMs it spawns: the surefire fork, Karaf containers, WildFly servers etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8839) ClusterTopologyManagerImplTest leaks threads

by Dan Berindei (JIRA)

Dan Berindei created ISPN-8839: ---------------------------------- Summary: ClusterTopologyManagerImplTest leaks threads Key: ISPN-8839 URL: https://issues.jboss.org/browse/ISPN-8839 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 9.2.0.CR2 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 9.2.0.CR3 Both test methods create an {{ExecutorService}} but don't shut it down. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8802) Improve documentation on client-side marshalling protection

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8802?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8802: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5767 > Improve documentation on client-side marshalling protection > ----------------------------------------------------------- > > Key: ISPN-8802 > URL: https://issues.jboss.org/browse/ISPN-8802 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.0.Final > > > We should make cleared the fact that marshalling protection is opt-in and explain how {{addJavaSerialWhiteList}} works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7011: ------------------------------- Status: Open (was: New) > @AfterClass cleanup doesn't work with @InTransactionMode or @InCacheMode > ------------------------------------------------------------------------ > > Key: ISPN-7011 > URL: https://issues.jboss.org/browse/ISPN-7011 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.2.0.Final > > > Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation). > Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure: > {noformat} > java.lang.IllegalStateException: Two tests with the same name running in parallel: test > at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88) > at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115) > 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:498) > 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.invokeConfigurations(Invoker.java:138) > at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8822) Performance degradation when running Spark jobs

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8822?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-8822 at 2/19/18 2:36 AM: ------------------------------------------------------------------ Indeed, my proposal is to call shutdowngracefully() with an infinitesimal amount of time and make close() not wait for any new potential new task. At least in Spark, there is no possibility of that happen, once I close the RCM no tasks will ever be aubmitted. was (Author: gustavonalle): Indeed, my proposal is to call shutdowngracefully() with an infinitesimal small of time and make close() not wait for any new potential new task. At least in Spark, there is no possibility of that happen, once I close the RCM no tasks will ever be aubmitted. > Performance degradation when running Spark jobs > ----------------------------------------------- > > Key: ISPN-8822 > URL: https://issues.jboss.org/browse/ISPN-8822 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.2.0.CR2 > Reporter: Gustavo Fernandes > > When trying to upgrade the [Spark connector |https://github.com/infinispan/infinispan-spark/] to use Infinispan 9.2.0.CR2, the test suite runs about 10x slower. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8822) Performance degradation when running Spark jobs

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8822?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-8822 at 2/19/18 2:36 AM: ------------------------------------------------------------------ Indeed, my proposal is to call shutdowngracefully() with an infinitesimal amount of time and make close() not wait for any potential new task. At least in Spark, there is no possibility of that happen, once I close the RCM no tasks will ever be aubmitted. was (Author: gustavonalle): Indeed, my proposal is to call shutdowngracefully() with an infinitesimal amount of time and make close() not wait for any new potential new task. At least in Spark, there is no possibility of that happen, once I close the RCM no tasks will ever be aubmitted. > Performance degradation when running Spark jobs > ----------------------------------------------- > > Key: ISPN-8822 > URL: https://issues.jboss.org/browse/ISPN-8822 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.2.0.CR2 > Reporter: Gustavo Fernandes > > When trying to upgrade the [Spark connector |https://github.com/infinispan/infinispan-spark/] to use Infinispan 9.2.0.CR2, the test suite runs about 10x slower. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018