September 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2321) Memory leak in CacheStoreInterceptor (cache with LockingMode.PESSIMISTIC)

by Carsten Lohmann (JIRA)

Carsten Lohmann created ISPN-2321: ------------------------------------- Summary: Memory leak in CacheStoreInterceptor (cache with LockingMode.PESSIMISTIC) Key: ISPN-2321 URL: https://issues.jboss.org/browse/ISPN-2321 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.2.0.Alpha3 Reporter: Carsten Lohmann Assignee: Mircea Markus We noticed a memory leak in CacheStoreInterceptor where the "txStores" and "preparingTxs" maps get not cleaned up after a transaction is completed and org.infinispan.transaction.xa.GlobalTransaction objects accumulate in these maps. This occurs in connection with transactional caches with pessimistic locking. See attached test case. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] (ISPN-2295) Inject the running Cache in the PreExecute context for Reducer operations

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2295: ------------------------------------- Summary: Inject the running Cache in the PreExecute context for Reducer operations Key: ISPN-2295 URL: https://issues.jboss.org/browse/ISPN-2295 Project: Infinispan Issue Type: Feature Request Components: Distributed Execution and Map/Reduce Reporter: Sanne Grinovero Assignee: Vladimir Blagojevic Fix For: 5.2.0.Alpha4, 5.2.0.Final Change the _org.infinispan.distexec.mapreduce.spi.MapReduceTaskLifecycle_ to pass the Cache as it does with _Mapper_ also to _Reducer_ instances. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] (ISPN-1440) Infinispan query module - index rebuild

by Juan Ignacio Barisich (Created) (JIRA)

Infinispan query module - index rebuild --------------------------------------- Key: ISPN-1440 URL: https://issues.jboss.org/browse/ISPN-1440 Project: Infinispan Issue Type: Feature Request Components: Lucene Directory, Querying Affects Versions: 5.1.0.ALPHA1 Environment: N/S Reporter: Juan Ignacio Barisich Assignee: Manik Surtani Add an index rebuild feature to the Infinispan Query module. This is neccesary when, for example, the index mapping changes, so it is neccesary to take a full rebuild for update the index entries with this changes. Is suggested to introduce an equivalent of Hibernate Search's "MassIndexer" API (http://docs.jboss.org/hibernate/search/3.3/reference/en-US/html_single/#s...). -- 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

11 years, 7 months

4
9
0 / 0

[JBoss JIRA] (ISPN-2294) Duplicate index entries when using the Infinispan IndexManager query backend

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2294: ------------------------------------- Summary: Duplicate index entries when using the Infinispan IndexManager query backend Key: ISPN-2294 URL: https://issues.jboss.org/browse/ISPN-2294 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.2.0.Alpha3 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.Alpha4 The custom commands driven Query backend does not transform Document Ids using the keyTransformer component: depending on which node is the master, document ids in string form might not match the existing document for the same entry, creating duplicates in the index. This is user visible only as an unexpected number of matches in an index but should not result in duplicate entries; could have returned less entries than those requested at the current page when using pagination on the query results. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2314) QueryCacheRestartTest test failure

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2314: ----------------------------------- Summary: QueryCacheRestartTest test failure Key: ISPN-2314 URL: https://issues.jboss.org/browse/ISPN-2314 Project: Infinispan Issue Type: Feature Request Components: Test Suite Affects Versions: 5.2.0.Alpha3 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Alpha4 Query tests fail with messages like: {quote}testLocalQueryCacheRestart(org.infinispan.query.blackbox.QueryCacheRestartTest): It was expected to find the Query interceptor registered in the InterceptorChain but it wasn't found {quote} This was working fine in https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/814/co..., so since the issue appears to be related to cache startup, it's almost for sure related to ISPN-2256 (appeared in https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/815/co...). Btw, as part of fixing up ISPN-2290 to avoid duplicate domains, I'm making the tests that caused the testsuite to halt more resilient. -- 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, 7 months

3
8
0 / 0

[JBoss JIRA] (ISPN-2184) infinispan dependencies are missing in maven central

by Radim Kolář (JIRA)

Radim Kolář created ISPN-2184: --------------------------------- Summary: infinispan dependencies are missing in maven central Key: ISPN-2184 URL: https://issues.jboss.org/browse/ISPN-2184 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 5.1.5.FINAL Environment: Maven 3 Reporter: Radim Kolář Assignee: Manik Surtani Priority: Blocker I am using maven 3 to resolve dependencies for my project. I have dependency only on core. <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-core</artifactId> </dependency> Maven complains about [WARNING] The POM for org.rhq.helpers:rhq-pluginAnnotations:jar:3.0.4 is missing , no dependency information available because in maven central repo there is no org.rhq stuff at all. Its against maven central repo policy because all dependencies must be uploaded there as well. Please upload missing artefact or mark them as optional in your pom. -- 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

11 years, 7 months

2
7
0 / 0

[JBoss JIRA] (ISPN-1821) Infinispan should be able to parse configuration in the AS7/EAP/EDG style

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-1821: ------------------------------------- Summary: Infinispan should be able to parse configuration in the AS7/EAP/EDG style Key: ISPN-1821 URL: https://issues.jboss.org/browse/ISPN-1821 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.FINAL -- 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

11 years, 7 months

2
4
0 / 0

[JBoss JIRA] (ISPN-2149) FineGrainedAtomicMap implementation fails to consider removal of elements

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2149: ------------------------------------- Summary: FineGrainedAtomicMap implementation fails to consider removal of elements Key: ISPN-2149 URL: https://issues.jboss.org/browse/ISPN-2149 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.2.0.ALPHA1, 5.1.5.FINAL Reporter: Sanne Grinovero Assignee: Vladimir Blagojevic Priority: Critical Fix For: 5.2.0.ALPHA2 Most methods in the {{org.infinispan.atomic.FineGrainedAtomicHashMapProxy<K, V>}} implementation seem to ignore the use case of removing keys from the map. {{keySet()}}, {{values()}}, {{entrySet()}}, {{size()}}, {{isEmpty()}} all ignore the fact that values in the uncommitted map might have been *removed* in the current transaction, or have *intersections* with existing keys. Note that failing to consider intersections has it return the wrong entries as committed values overwrite the in-flight values. Methods like {{containsKey}} don't check if the matched key is in fact stored in the {{DeltaAwareCacheEntry}} as a deleted entry. -- 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

11 years, 7 months

5
9
0 / 0

[JBoss JIRA] Created: (ISPN-374) Add event handling to Hot Rod

by Galder Zamarreno (JIRA)

Add event handling to Hot Rod ----------------------------- Key: ISPN-374 URL: https://jira.jboss.org/jira/browse/ISPN-374 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.1.0.BETA1, 5.1.0.Final Enable Hot Rod servers to send events asynchronously to registered clients over persistent connections. This would allow use cases such as clients maintaining L1 caches and these events could be used for servers to invalidate keys on the client side. See dev list thread for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
8
0 / 0

[JBoss JIRA] (ISPN-2238) DistributedExecutable setEnvironment for local executed tasks is always empty

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2238: ---------------------------------- Summary: DistributedExecutable setEnvironment for local executed tasks is always empty Key: ISPN-2238 URL: https://issues.jboss.org/browse/ISPN-2238 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.1.6.FINAL Reporter: Thomas Fromm Assignee: Mircea Markus When executing a DistributedCallable everywhere, the local executed one gets always empty Set of keys at setEnvironment. There's a keyMapping missed, which fills the set at least with the keys where the local node is owner. Testcase attached. -- 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, 7 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2012