July 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1245) Topology cache updates on stop should be asynchronous

by Galder Zamarreño (JIRA)

Topology cache updates on stop should be asynchronous ----------------------------------------------------- Key: ISPN-1245 URL: https://issues.jboss.org/browse/ISPN-1245 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.CR7 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.FINAL Topology cache updates when a server stops not only need Flag.FAIL_SILENTLY, Flag.ZERO_LOCK_ACQUISITION_TIMEOUT flags, but also need Force.FORCE_ASYNCHRONOUS to avoid waiting from replies from other nodes. Remember that there's a crashed member view listener running in the coordinator of the cluster that checks whether the view was not updated and whether any old members are still lingering in the view, and updates it accordingly. It could happen that the coordinator has the right view, cos the node on stop updated its view, but not another node's view. This is not too bad cos the client could do a failover if a node is not available and it'd get eventually a new view. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1225) check the length of vint/vlong values in hotrod protocol

by Michal Linhard (JIRA)

check the length of vint/vlong values in hotrod protocol -------------------------------------------------------- Key: ISPN-1225 URL: https://issues.jboss.org/browse/ISPN-1225 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.CR7 Reporter: Michal Linhard Assignee: Galder Zamarreño Currently no check is done on the length of the VInt/VLong values that are transmitted in messages of Hot Rod protocol. (the next byte is read until its MSB is 0) We could limit the length of the VInt value to 5 bytes and VLong to 9 bytes and throw an exception like "stream corrupted" if the limit is exceeded, for the purposes of input data validation ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-1233) Regression in ClusterIdGenerator

by Trustin Lee (JIRA)

Regression in ClusterIdGenerator -------------------------------- Key: ISPN-1233 URL: https://issues.jboss.org/browse/ISPN-1233 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.0.0.CR7 Reporter: Trustin Lee Assignee: Manik Surtani Fix For: 5.0.0.FINAL Memcached replication tests show a regression https://hudson.qa.jboss.com/hudson/view/EDG6/job/edg-60-functional-dist-m... ClusterIdGenerator throws java.lang.IllegalStateException: If clustered, Version prefix cannot be 0. Rank calculator probably not in use. The issue exists in both CR6 and CR7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic

by Tero Heinonen (JIRA)

Affinity accross caches - static or dynamic ------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups) -- 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

12 years, 9 months

7
23
0 / 0

[JBoss JIRA] Created: (ISPN-312) Ability to group data entries

by Mindaugas Žakšauskas (JIRA)

Ability to group data entries ----------------------------- Key: ISPN-312 URL: https://jira.jboss.org/jira/browse/ISPN-312 Project: Infinispan Issue Type: Feature Request Components: Core API, Distributed Cache, Eviction, Locking and Concurrency Affects Versions: 4.0.0.CR2 Reporter: Mindaugas Žakšauskas Assignee: Manik Surtani Priority: Minor This is a spin-off from http://lists.jboss.org/pipermail/infinispan-dev/2009-December/001968.html. The requested feature would allow distinct entries to be assigned to custom arbitrary groups. Later in time those groups could be flushed on demand without any knowledge of entry keys. This feature exists in other open source cache library, see: http://www.opensymphony.com/oscache/api/com/opensymphony/oscache/base/Cac... -- 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

12 years, 9 months

7
15
0 / 0

[JBoss JIRA] Created: (ISPN-1241) Ignore IllegalState exceptions for invalidation commands

by Sanne Grinovero (JIRA)

Ignore IllegalState exceptions for invalidation commands ---------------------------------------------------------- Key: ISPN-1241 URL: https://issues.jboss.org/browse/ISPN-1241 Project: Infinispan Issue Type: Enhancement Components: Distributed Cache Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.0.0.FINAL We should ignore errors about Invalidation messages not being applied, such as: {code}2011-07-14 15:16:20,940 ERROR [RebalanceTask] (Rehasher,Infinispan-Cluster,NonStringKeyStateTransferTest-NodeC-7649) ISPN000145: Error during rehash java.lang.IllegalStateException: Default cache is in 'STOPPING' state and this is an invocation not belonging to an on-going transaction, so it does not accept new invocations. Either restart it or recreate the cache container. at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:83) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:64) at org.infinispan.commands.AbstractVisitor.visitInvalidateCommand(AbstractVisitor.java:120) at org.infinispan.commands.AbstractVisitor.visitInvalidateL1Command(AbstractVisitor.java:124) at org.infinispan.commands.write.InvalidateL1Command.acceptVisitor(InvalidateL1Command.java:177) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:274) at org.infinispan.distribution.RebalanceTask.invalidateKeys(RebalanceTask.java:172) at org.infinispan.distribution.RebalanceTask.performRehash(RebalanceTask.java:145) at org.infinispan.distribution.RehashTask.call(RehashTask.java:67) at org.infinispan.distribution.RehashTask.call(RehashTask.java:44) 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:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662){code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1199) RemoteCacheManager failure in multi-threaded environment with maxActive=Integer.MAX_VALUE

by Michal Linhard (JIRA)

RemoteCacheManager failure in multi-threaded environment with maxActive=Integer.MAX_VALUE ----------------------------------------------------------------------------------------- Key: ISPN-1199 URL: https://issues.jboss.org/browse/ISPN-1199 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.CR5 Reporter: Michal Linhard Assignee: Manik Surtani I get erros like these, when I run test with 100 threads using either shared or multiple remote cache managers: {code} java.lang.IllegalStateException: We should not reach here! at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:73) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:201) at org.infinispan.CacheSupport.put(CacheSupport.java:51) at org.jboss.edg.test.MultiThreadedManualTest$Runner.run(MultiThreadedManualTest.java:77) {code} The cause in my environment came to connection-pool configuration property "maxActive" clients set to Integer.MAX_VALUE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (ISPN-1240) Fix Remote CacheStore test setup

by Sanne Grinovero (JIRA)

Fix Remote CacheStore test setup -------------------------------- Key: ISPN-1240 URL: https://issues.jboss.org/browse/ISPN-1240 Project: Infinispan Issue Type: Task Components: Test Suite Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.0.0.FINAL Fixing this issue: https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/125/or... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1236) Custom interceptors initialization issue

by Mircea Markus (JIRA)

Custom interceptors initialization issue ---------------------------------------- Key: ISPN-1236 URL: https://issues.jboss.org/browse/ISPN-1236 Project: Infinispan Issue Type: Bug Affects Versions: 4.2.1.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.0.0.FINAL, 5.0.0.CR7 @Start and @Inject annotations are being ignored on the custom interceptors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-1234) Cleanup and updated dependencies

by Sanne Grinovero (JIRA)

Cleanup and updated dependencies -------------------------------- Key: ISPN-1234 URL: https://issues.jboss.org/browse/ISPN-1234 Project: Infinispan Issue Type: Task Components: Build process Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.0.0.FINAL Some dependencies are no longer needed, some could need a version update. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2011