May 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2074) The consistent hash in the java Hotrod client is buggy

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2074: ----------------------------------- Summary: The consistent hash in the java Hotrod client is buggy Key: ISPN-2074 URL: https://issues.jboss.org/browse/ISPN-2074 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.5.CR1, 5.2.0.ALPHA1 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.5.FINAL, 5.2.0.FINAL If the normalised consistent hash of the key has value equal to 0 then an incorrect node is returned. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] (ISPN-2045) Upgrade to JGroups 3.0.10

by Manik Surtani (JIRA)

Manik Surtani created ISPN-2045: ----------------------------------- Summary: Upgrade to JGroups 3.0.10 Key: ISPN-2045 URL: https://issues.jboss.org/browse/ISPN-2045 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 5.1.4.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.5.FINAL JGroups 3.0.10 contains: The 9 issues are listed at [1]. The most important issues were: - https://issues.jboss.org/browse/JGRP-1455: if there was heavy load while joining a cluster, the joiner might lose the initial message - SEQUENCER related bug fixes - Timer fix: https://issues.jboss.org/browse/JGRP-1457 - Performance fix for TCP: https://issues.jboss.org/browse/JGRP-1462 - Stats for RpcDispatcher, list all sync and async RPCs: https://issues.jboss.org/browse/JGRP-1456 [1] https://issues.jboss.org/browse/JGRP/fixforversion/12319346 -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] (ISPN-35) JSR107 compliant API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño commented on ISPN-35: -------------------------------------- JSR-107 comes with a new cache event notifiers for which we'll need to provide an implementation. This is a great opportunity for this implementation to avoid the following issues that have been hurting our users, including moi: 1. Have a real difference between notifications when a cache entry is created, and when an existing cache entry is modified, and make use cases like the one explained in http://lists.jboss.org/pipermail/infinispan-dev/2012-February/010272.html are easy to achieve, without the need for clients to keep state. 2. Provide guarantees with regards to cache contents and cache size for cache listener implementers. This is related to ISPN-2054, and my comment on ISPN-1948 with regards to cache size guarantees. > JSR107 compliant API > -------------------- > > Key: ISPN-35 > URL: https://issues.jboss.org/browse/ISPN-35 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 6.0.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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-35) JSR107 compliant API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño reopened ISPN-35: ---------------------------------- Re-opening, JSR-107 is alive and kicking... > JSR107 compliant API > -------------------- > > Key: ISPN-35 > URL: https://issues.jboss.org/browse/ISPN-35 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 6.0.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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-35) JSR107 compliant API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated ISPN-35: --------------------------------- Fix Version/s: 6.0.0.FINAL Tentatively... > JSR107 compliant API > -------------------- > > Key: ISPN-35 > URL: https://issues.jboss.org/browse/ISPN-35 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 6.0.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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2036) ClassCastException during TreeCache instantiation

by Michael Gronau (JIRA)

Michael Gronau created ISPN-2036: ------------------------------------ Summary: ClassCastException during TreeCache instantiation Key: ISPN-2036 URL: https://issues.jboss.org/browse/ISPN-2036 Project: Infinispan Issue Type: Bug Components: Core API, Tree API Affects Versions: 5.1.4.FINAL Reporter: Michael Gronau Assignee: Manik Surtani With the current version it is not possible to create an instance of TreeCache. I'm using the cache inside JBoss 7.1.2 Final. The following lines worked in earlier versions of the cache api: org.infinispan.Cache<String, Object> infiniCache = this.cacheContainer.getCache(cfg.getName()); TreeCache<String, Object> tc = new TreeCacheFactory().createTreeCache(infiniCache.getAdvancedCache()); Now the method createTreeCache(..) throws an java.lang.IllegalArgumentException: This adapter only works with CacheImpl, not with DelegatingCach e -- 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, 11 months

4
22
0 / 0

[JBoss JIRA] (ISPN-1588) IndexOutOfBoundsException while using clustered query

by Mathieu Lachance (Created) (JIRA)

IndexOutOfBoundsException while using clustered query ----------------------------------------------------- Key: ISPN-1588 URL: https://issues.jboss.org/browse/ISPN-1588 Project: Infinispan Issue Type: Bug Components: Querying, RPC Affects Versions: 5.1.0.BETA5 Reporter: Mathieu Lachance Assignee: Sanne Grinovero when using clustered query with dist sync mode i'm running into index out of bound exception. java.lang.IndexOutOfBoundsException: Index: 100, Size: 100 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.infinispan.query.clustered.DistributedIterator.current(DistributedIterator.java:138) at org.infinispan.query.clustered.DistributedIterator.next(DistributedIterator.java:114) at org.infinispan.query.clustered.ClusteredCacheQueryImpl.list(ClusteredCacheQueryImpl.java:136) at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:239) at com.XXX.DistributedCache.cacheQueryList(DistributedCache.java:200) at com.XXX.ClientCache.getClientsByServerId(ClientCache.java:168) at com.XXX.getClientsByServerId(ClientManager.java:157) at com.XXX$PingClient.run(PlayerBll.java:890) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) i do not have any reproductible step, but here's what i know : it only seems to happen under high contention ; when i'm running stress test. when running a stress test i might get query that return over than 100 results. tough i've also seen it happen on query that can only return few (4-6) results. i never saw the stack trace with different index and size different than 100 (it's always the exact same exception). i've also tried the lazy iterator to see if it would have a different behavior, but i get the same stack trace. is there anything i could look up in the source code to debug and maybe find the repro steps ? thanks, -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1980) Distributed Queries problem when results size could be greater than HsQuery.maxResults

by Israel Lacerra (JIRA)

Israel Lacerra created ISPN-1980: ------------------------------------ Summary: Distributed Queries problem when results size could be greater than HsQuery.maxResults Key: ISPN-1980 URL: https://issues.jboss.org/browse/ISPN-1980 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.1.4.CR1 Reporter: Israel Lacerra Assignee: Sanne Grinovero When a distributed query could get more results than HSQuery.maxResults, an exception is thrown: Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 200, Size: 200 at java.util.ArrayList.rangeCheck(ArrayList.java:571) at java.util.ArrayList.get(ArrayList.java:349) at org.infinispan.query.clustered.DistributedIterator.current(DistributedIterator.java:140) at org.infinispan.query.clustered.DistributedIterator.next(DistributedIterator.java:116) The correct behaviour is to limit the results up to HsQuery.maxResults -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] (ISPN-2067) The ConsistentHash implementation on the hotrod client is very inefficient

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2067: ----------------------------------- Summary: The ConsistentHash implementation on the hotrod client is very inefficient Key: ISPN-2067 URL: https://issues.jboss.org/browse/ISPN-2067 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.4.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.5.FINAL, 5.2.0.ALPHA1 Profiler snapshots show that a large amount of time is spent in the {{org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV1#getServer}} method (about 13%). The root cause of this is the fact that the size method invoked on an object returned by TreeMap.tail() is very expensive: TreeMap.tail() returns an instance of TreeMap.AscendingSubMap class for which the size method, in order to calculates the number of elements, iterates over the entire collection(O(n)). This is highly inefficient and not scalable especially since the number of virtual nodes was set to 50 by default, as not the size of the collection is quite high: e.g. 32 nodes with 50 virtual nodes each, size()'s iterates an average of ~750 elements. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2060) Versioning configuration not read when cache configuration is retrieved

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2060: -------------------------------------- Summary: Versioning configuration not read when cache configuration is retrieved Key: ISPN-2060 URL: https://issues.jboss.org/browse/ISPN-2060 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.5.CR1, 5.1.4.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.5.FINAL Test: {code}@Test(groups = "unit", testName = "BootTest") public class BootTest extends SingleCacheManagerTest { @Override protected EmbeddedCacheManager createCacheManager() throws Exception { return TestCacheManagerFactory.fromXml("infinispan.xml"); } public void test000() { new TreeCacheFactory().createTreeCache(cache); } }{code} XML: {code}<infinispan> <default> <locking isolationLevel="REPEATABLE_READ" lockAcquisitionTimeout="15000" writeSkewCheck="true"/> <transaction transactionManagerLookupClass="org.infinispan.transaction.lookup.GenericTransactionManagerLookup" transactionMode="TRANSACTIONAL" lockingMode="OPTIMISTIC"/> <invocationBatching enabled="true"/> <versioning versioningScheme="SIMPLE" enabled="true" /> <clustering mode="LOCAL"/> </default> <namedCache name="JCoffeeSystemCache"> <versioning versioningScheme="SIMPLE" enabled="true" /> </namedCache> </infinispan> {code} -- 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, 11 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2012