October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2181) Allow to inject the current cache into Mapper/Reducer/Callable objects

by Nicolas Filotto (JIRA)

Nicolas Filotto created ISPN-2181: ------------------------------------- Summary: Allow to inject the current cache into Mapper/Reducer/Callable objects Key: ISPN-2181 URL: https://issues.jboss.org/browse/ISPN-2181 Project: Infinispan Issue Type: Enhancement Components: CDI integration Affects Versions: 5.2.0.ALPHA2 Reporter: Nicolas Filotto Assignee: Pete Muir Thanks to ISPN-1636, it is now possible to inject the cache into Mapper/Reducer/Callable objects however the cache injected is the default cache not the cache for which the MapReduceTask/DistributedExecutorService has been created which is quite error prone since we don't expect to get the default cache but the current cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
17
0 / 0

[JBoss JIRA] (ISPN-2369) CLI improvements

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2369: ------------------------------------- Summary: CLI improvements Key: ISPN-2369 URL: https://issues.jboss.org/browse/ISPN-2369 Project: Infinispan Issue Type: Enhancement Reporter: Tristan Tarrant Assignee: Tristan Tarrant Add various improvements to the CLI New commands: info, stats, upgrade, create Better command-line completion -- 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

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] (ISPN-2401) StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2401: ---------------------------------- Summary: StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer Key: ISPN-2401 URL: https://issues.jboss.org/browse/ISPN-2401 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.Beta2 Reporter: Dan Berindei Assignee: Adrian Nistor Fix For: 5.2.0.Final They only check the segments that are in progress, so they return false if state transfer started but didn't add any segment to the in-progress list yet. If isStateTransferInProgressForKey is fixed, DistributionManagerImpl.getLocality should be changed to use it again. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2390) CLI connector should support JMX over Remoting

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2390: ------------------------------------- Summary: CLI connector should support JMX over Remoting Key: ISPN-2390 URL: https://issues.jboss.org/browse/ISPN-2390 Project: Infinispan Issue Type: Feature Request Components: CLI Affects Versions: 5.2.0.Beta1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Critical Fix For: 5.2.0.CR1 -- 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

12 years, 3 months

3
2
0 / 0

[JBoss JIRA] (ISPN-2203) Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2203: -------------------------------------- Summary: Test AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle is unstable Key: ISPN-2203 URL: https://issues.jboss.org/browse/ISPN-2203 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Tomas Sykora Fix For: 5.2.0.ALPHA3 Test being disabled as part of ISPN-2196 cos it's unstable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2400) ReceiveBufferSize has no effect in WebSocketServer

by Norman Maurer (JIRA)

Norman Maurer created ISPN-2400: ----------------------------------- Summary: ReceiveBufferSize has no effect in WebSocketServer Key: ISPN-2400 URL: https://issues.jboss.org/browse/ISPN-2400 Project: Infinispan Issue Type: Feature Request Reporter: Norman Maurer Assignee: Mircea Markus The problem is that the ReceiveBufferSize is set on the "Acceptor Channel", but should be set on the "Child Channel". -- 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

12 years, 3 months

2
3
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.Beta2) > 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

12 years, 3 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.Beta2) > 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

12 years, 3 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.Beta2) > 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2383) Transactions incorrectly removed by the StaleTransactionCleanupService causing inconsistencies

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2383: ----------------------------------- Summary: Transactions incorrectly removed by the StaleTransactionCleanupService causing inconsistencies Key: ISPN-2383 URL: https://issues.jboss.org/browse/ISPN-2383 Project: Infinispan Issue Type: Bug Components: State transfer Reporter: Mircea Markus Assignee: Mircea Markus Priority: Critical Fix For: 5.2.0.CR1 - tx runs on N1, prepare a single-key tx (k1) on N2 - block commit execution on N2 and start N3 so that k1 node maps to N3 - the StaleTransactionCleanupService[1] removes the transaction from N2 - when commit is executed there's no tx on N2 to forward the commit to so it simply does nothing - the TxCompletionNotification arrives on N3 and rollbacks the uncommitted data - data is lost! Solution: the StaleTransactionCleanupService should not run concurrently with the NBST but only after the NBST is finished. I.e. it should no longer be an topology listener, but should be invoked explicitly during the NBST-complete RPC. -- 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

12 years, 3 months

3
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012