May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3085) ExpiryTest intermittent failure

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3085?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3085: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1812 > ExpiryTest intermittent failure > ------------------------------- > > Key: ISPN-3085 > URL: https://issues.jboss.org/browse/ISPN-3085 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.2.6.Final > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Beta2 > > > java.lang.NullPointerException > at org.infinispan.expiry.ExpiryTest.testLifespanExpiryInPutIfAbsent(ExpiryTest.java:153) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > 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:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2218) Create maven-only release script

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2218?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2218: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1800 > Create maven-only release script > -------------------------------- > > Key: ISPN-2218 > URL: https://issues.jboss.org/browse/ISPN-2218 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Fix For: 6.0.0.Final > > > Create a reduced version of release.py to do Maven-only releases. Make sure as much as code is shared with the existing release.py script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2218) Create maven-only release script

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-2218?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2218: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.3.0.Beta2 5.3.0.Final (was: 6.0.0.Final) Resolution: Done > Create maven-only release script > -------------------------------- > > Key: ISPN-2218 > URL: https://issues.jboss.org/browse/ISPN-2218 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > Create a reduced version of release.py to do Maven-only releases. Make sure as much as code is shared with the existing release.py script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3086) Infinite loop when creating more than two Distributed Cache nodes

by Balazs Zsoldos (JIRA)

Balazs Zsoldos created ISPN-3086: ------------------------------------ Summary: Infinite loop when creating more than two Distributed Cache nodes Key: ISPN-3086 URL: https://issues.jboss.org/browse/ISPN-3086 Project: Infinispan Issue Type: Feature Request Components: JCache Affects Versions: 5.3.0.Beta1 Reporter: Balazs Zsoldos Assignee: Mircea Markus I created a very simple application based on https://docs.jboss.org/author/display/ISPN/Using+Infinispan+as+a+JCache+p... I changed the code to created distributed caches instead of replicated ones. It works until two nodes but if there are three nodes it starts an infinite loop. *The modified XML contains:* <namedCache name="namedCache"> <clustering mode="dist" /> </namedCache> *The modified java code contains:* CacheManager cacheManager1 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); CacheManager cacheManager2 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); CacheManager cacheManager3 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); *Symptom:* The code waits on the third command while there is an infinite loop on a background thread. I guess the benefit of distribution would come with more than two nodes but I cannot test it due to the problem above. Although I used infinispan via JCache I think this issue is not related to the JCache API but it comes from the infinispan core. *BTW:* Distributed caches seem to me about 30% slower than replicated caches concerning to put and delete functions with two nodes. I guess the -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3084) BaseBackupInterceptor creates new logger on every XSite call

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3084?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3084: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1811 > BaseBackupInterceptor creates new logger on every XSite call > ------------------------------------------------------------ > > Key: ISPN-3084 > URL: https://issues.jboss.org/browse/ISPN-3084 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.2.6.Final > Reporter: Erik Salter > Assignee: Mircea Markus > > The BaseBackupInterceptor creates a new logger instance on every transactional backup. This ends up slowing down the performance of the backup sender, resulting in degraded performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3084) BaseBackupInterceptor creates new logger on every XSite call

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3084?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3084: -------------------------------- Assignee: Erik Salter (was: Mircea Markus) > BaseBackupInterceptor creates new logger on every XSite call > ------------------------------------------------------------ > > Key: ISPN-3084 > URL: https://issues.jboss.org/browse/ISPN-3084 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.2.6.Final > Reporter: Erik Salter > Assignee: Erik Salter > > The BaseBackupInterceptor creates a new logger instance on every transactional backup. This ends up slowing down the performance of the backup sender, resulting in degraded performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3084) BaseBackupInterceptor creates new logger on every XSite call

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3084?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3084: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.3.0.Beta2 5.3.0.Final Resolution: Done > BaseBackupInterceptor creates new logger on every XSite call > ------------------------------------------------------------ > > Key: ISPN-3084 > URL: https://issues.jboss.org/browse/ISPN-3084 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.2.6.Final > Reporter: Erik Salter > Assignee: Erik Salter > Fix For: 5.3.0.Beta2, 5.3.0.Final > > > The BaseBackupInterceptor creates a new logger instance on every transactional backup. This ends up slowing down the performance of the backup sender, resulting in degraded performance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3085) ExpiryTest intermittent failure

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3085: ----------------------------------- Summary: ExpiryTest intermittent failure Key: ISPN-3085 URL: https://issues.jboss.org/browse/ISPN-3085 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 5.2.6.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Beta2 java.lang.NullPointerException at org.infinispan.expiry.ExpiryTest.testLifespanExpiryInPutIfAbsent(ExpiryTest.java:153) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) 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:334) at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3078) @AfterMethod/alwaysRun and alike are not used correctly

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3078?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3078: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > @AfterMethod/alwaysRun and alike are not used correctly > -------------------------------------------------------- > > Key: ISPN-3078 > URL: https://issues.jboss.org/browse/ISPN-3078 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.3.0.Beta1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Beta2 > > > alwaysRun=true makes the invocation of that method to happen even if the test that has the method is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#... > E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod. > This is causing the suite to exit: > {quote} > [14:53:10][org.infinispan:infinispan-server-core] > [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!! > [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!! > [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > {quote} > AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this. > > http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3080) upgrade to JGroups 3.3.0.Final

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3080?page=com.atlassian.jira.plugin.... ] Sanne Grinovero resolved ISPN-3080. ----------------------------------- Resolution: Done > upgrade to JGroups 3.3.0.Final > ------------------------------ > > Key: ISPN-3080 > URL: https://issues.jboss.org/browse/ISPN-3080 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Beta2, 5.3.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013