September 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7015) Make the ping port optional (assume the clusters are symmetric)

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7015: ----------------------------------------- Summary: Make the ping port optional (assume the clusters are symmetric) Key: ISPN-7015 URL: https://issues.jboss.org/browse/ISPN-7015 Project: Infinispan Issue Type: Sub-task Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7012) Refactor KUBE_PING

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7012: ----------------------------------------- Summary: Refactor KUBE_PING Key: ISPN-7012 URL: https://issues.jboss.org/browse/ISPN-7012 Project: Infinispan Issue Type: Feature Request Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7013) Prepare KUBE_PING for JGroups 4 release

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7013: ----------------------------------------- Summary: Prepare KUBE_PING for JGroups 4 release Key: ISPN-7013 URL: https://issues.jboss.org/browse/ISPN-7013 Project: Infinispan Issue Type: Sub-task Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7011: ------------------------------------ A simpler alternative to the `@InTransactionMode` annotation might be to check the tx mode in the test, similar to using {{Assume}} in JUnit: http://blog.xebia.com/conditionally-running-tests-in-testng/ > @AfterClass cleanup doesn't work with @InTransactionMode > -------------------------------------------------------- > > 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.0.0.Beta1 > > > 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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-7011 at 9/12/16 2:17 PM: ------------------------------------------------------------- TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest \(x\)}}. was (Author: dan.berindei): TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest (x)}}. > @AfterClass cleanup doesn't work with @InTransactionMode > -------------------------------------------------------- > > 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.0.0.Beta1 > > > 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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7011: ------------------------------------ TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest (x)}}. > @AfterClass cleanup doesn't work with @InTransactionMode > -------------------------------------------------------- > > 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.0.0.Beta1 > > > 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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-7011: ---------------------------------- Assignee: Dan Berindei > @AfterClass cleanup doesn't work with @InTransactionMode > -------------------------------------------------------- > > 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.0.0.Beta1 > > > 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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7011: ---------------------------------- Summary: @AfterClass cleanup doesn't work with @InTransactionMode Key: ISPN-7011 URL: https://issues.jboss.org/browse/ISPN-7011 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: Dan Berindei Priority: Minor Fix For: 9.0.0.Beta1 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 (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7010) Java Batch support

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7010: ----------------------------------------- Summary: Java Batch support Key: ISPN-7010 URL: https://issues.jboss.org/browse/ISPN-7010 Project: Infinispan Issue Type: Feature Request Components: Integration Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Investigate how to integrate Infinispan with [Java Batch|https://jcp.org/en/jsr/detail?id=352] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7009) Spring session integration

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7009: ----------------------------------------- Summary: Spring session integration Key: ISPN-7009 URL: https://issues.jboss.org/browse/ISPN-7009 Project: Infinispan Issue Type: Feature Request Components: Spring Integration Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016