October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2440) JGroupsTransport.invokeRemotely can throw SuspectExceptions even in SYNCHRONOUS_IGNORE_LEAVERS mode

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2440: ---------------------------------- Summary: JGroupsTransport.invokeRemotely can throw SuspectExceptions even in SYNCHRONOUS_IGNORE_LEAVERS mode Key: ISPN-2440 URL: https://issues.jboss.org/browse/ISPN-2440 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 5.2.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.CR1 In 5.1 we had a ResponseFilter for the "ignore leavers" case, which avoided throwing the SuspectedException. Because of NBST I had to disable the filter, but I didn't realize that it would cause SuspectedException to reappear. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1042) Ensure proper remote distributed task interruption/cancellation

by Vladimir Blagojevic (JIRA)

Ensure proper remote distributed task interruption/cancellation ---------------------------------------------------------------- Key: ISPN-1042 URL: https://issues.jboss.org/browse/ISPN-1042 Project: Infinispan Issue Type: Task Components: Distributed Cache Affects Versions: 5.0.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.0.0.CR1 We need to implement remote task interruption and cancellation for distributed executors and map reduce. Also, implement a proper shutdown of DistributedExecutorService. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
9
0 / 0

[JBoss JIRA] (ISPN-2351) Operate the Query MassIndexer via JMX

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2351?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2351: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta3) > Operate the Query MassIndexer via JMX > ------------------------------------- > > Key: ISPN-2351 > URL: https://issues.jboss.org/browse/ISPN-2351 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management, Querying > Reporter: Sanne Grinovero > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > > The MassIndexer is not exposed on JMX, we should expose it. -- 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-2354) AsyncStoreFunctionalTest fails intermittently

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2354?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2354: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta3) > AsyncStoreFunctionalTest fails intermittently > --------------------------------------------- > > Key: ISPN-2354 > URL: https://issues.jboss.org/browse/ISPN-2354 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.0.Alpha4 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR1 > > > AsyncStoreFunctionalTest sometimes fails with this assertion error: > {noformat} > 14:49:46,380 ERROR (testng-AsyncStoreFunctionalTest:) [UnitTestTestNGListener] Test testGetAfterRemove(org.infinispan.loaders.decorators.AsyncStoreFunctionalTest) failed. > java.lang.AssertionError: Keys not empty: [1] > at org.testng.AssertJUnit.fail(AssertJUnit.java:57) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:22) > at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest$3.call(AsyncStoreFunctionalTest.java:211) > at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1252) > at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest.testGetAfterRemove(AsyncStoreFunctionalTest.java:165) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {noformat} -- 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-2352) Second invocation of ClusteredQueryImpl.lazyIterator() yields results in reverse order

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2352?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2352: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta3) > Second invocation of ClusteredQueryImpl.lazyIterator() yields results in reverse order > -------------------------------------------------------------------------------------- > > Key: ISPN-2352 > URL: https://issues.jboss.org/browse/ISPN-2352 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.0.Alpha4 > Reporter: Marko Lukša > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 5.2.0.CR1 > > > When you invoke lazyIterator() for the 2nd time on the same ClusteredQueryImpl instance, the iterator returns results in reverse order. This only occurs when the query has a Sort specified. > Caused by DistributedIterator.setTopDocs(), which inverts the reverse flag on SortField. > The same is probably also true for ClusteredQueryImpl.iterator() -- 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-2456) Map/Reduce code and documentation uses both Combiner and Reducer interchangeably

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2456: ----------------------------------- Summary: Map/Reduce code and documentation uses both Combiner and Reducer interchangeably Key: ISPN-2456 URL: https://issues.jboss.org/browse/ISPN-2456 Project: Infinispan Issue Type: Feature Request Affects Versions: 6.0.0.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Beta3, 5.1.9.Final This is a bit confusing for people reading the code and the documentation, we should stick to a single name, i.e. reducer. -- 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
3
0 / 0

[JBoss JIRA] (ISPN-2455) CDI extension tests failing after upgrading to TestNG 6.7

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2455: ----------------------------------- Summary: CDI extension tests failing after upgrading to TestNG 6.7 Key: ISPN-2455 URL: https://issues.jboss.org/browse/ISPN-2455 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Beta3 After integrating ISPN-2450 the CDI extension test suite fails. This is because weld and arquillian rely on certain sl4j and testng versions. Rolling these versions back solved the problem: {code:xml} <version.slf4j.weld>1.5.10</version.slf4j.weld> <version.testng.arquillian>5.14.10</version.testng.arquillian> {code} -- 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
1
0 / 0

[JBoss JIRA] (ISPN-2450) Testsuite hanging because of parallel execution and TestNG bug

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2450: ------------------------------------- Summary: Testsuite hanging because of parallel execution and TestNG bug Key: ISPN-2450 URL: https://issues.jboss.org/browse/ISPN-2450 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Mircea Markus Fix For: 5.2.0.Beta3 I've had the testsuit hang frequently recently and it seems this stack is often found in such cases: > "pool-3-thread-14" prio=10 tid=0x00007f0d84632000 nid=0x1ce5 runnable > [0x00007f0d58a36000] > java.lang.Thread.State: RUNNABLE > at java.util.HashMap.put(HashMap.java:374) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:320) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) If after a while I take another thread dump, the thread is still looping around at the same line. I couldn't reproduce the problem with TestNG 6.7, not sure if they solved it or if it's just less likely. -- 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

3
5
0 / 0

[JBoss JIRA] (ISPN-2452) Module POMs should not use dependency versions from parent POM

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2452: ------------------------------------- Summary: Module POMs should not use dependency versions from parent POM Key: ISPN-2452 URL: https://issues.jboss.org/browse/ISPN-2452 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.2.0.Beta2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Beta3 -- 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

2
3
0 / 0

[JBoss JIRA] (ISPN-2381) Lock can be removed from map even when unlocked from non-owner

by Radim Vansa (JIRA)

Radim Vansa created ISPN-2381: --------------------------------- Summary: Lock can be removed from map even when unlocked from non-owner Key: ISPN-2381 URL: https://issues.jboss.org/browse/ISPN-2381 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Affects Versions: 5.2.0.Beta1 Reporter: Radim Vansa Assignee: Manik Surtani In OwnableReentrantLock: If in the tryRelease(int) the owner != requestor the lock is not unlocked, it is still removed from AbstractPerEntryLockContainer.locks causing that is effectively unlocked. https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- 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

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012