June 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1133) Core developer maven profile

by Galder Zamarreño (JIRA)

Core developer maven profile ---------------------------- Key: ISPN-1133 URL: https://issues.jboss.org/browse/ISPN-1133 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Optional Fix For: 5.0.0.CR4 It'd be nice to have a 'core-dev' profile in Maven that: - Skips the enforcer plugin - Skips generation of source jars This would speed up builds in either continous build or our local envs. Any more suggestions? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-1079) Allow users to specify a build directory

by Dan Berindei (JIRA)

Allow users to specify a build directory ---------------------------------------- Key: ISPN-1079 URL: https://issues.jboss.org/browse/ISPN-1079 Project: Infinispan Issue Type: Enhancement Affects Versions: 5.0.0.BETA2, 4.2.1.FINAL, 4.2.2.BETA1 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Optional Fix For: 4.2.2.FINAL, 5.0.0.CR1, 5.0.0.FINAL If a user wants to speed up the build by compiling to a ramdisk, he should be able to set the build directory in ~/.m2/settings.xml, something like this: <settings> <profiles> <profile> <properties> <buildDirectory>/tmp/privatebuild/${project.basedir}/${project.version}</buildDirectory> </properties> </profile> </profiles> </settings> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (ISPN-1143) Make Apache Avro dependency optional

by Galder Zamarreño (JIRA)

Make Apache Avro dependency optional ------------------------------------ Key: ISPN-1143 URL: https://issues.jboss.org/browse/ISPN-1143 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR4 The Hot Rod client only needs it if you're gonna configure the apache avro marshaller, so should be optional or provided. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1127) Memory leak in CacheStoreInterceptor

by Sergey Kondratyev (JIRA)

Memory leak in CacheStoreInterceptor ------------------------------------ Key: ISPN-1127 URL: https://issues.jboss.org/browse/ISPN-1127 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.0.0.CR3, 4.2.1.FINAL Reporter: Sergey Kondratyev Assignee: Manik Surtani CacheStoreInterceptor leaks org.infinispan.transaction.xa.GlobalTransaction objects. Amount of live org.infinispan.transaction.xa.GlobalTransaction objects is climbing during cache work. It is possible due to two reasons: 1. when cache is in async replication mode entries from both txStores and preparingTxs are never deleted (maybe like JBCACHE-1454 ?). 2. when cache is in sync mode (I tested on dist sync mode), entries from preparingTxs are not deleted in commit method (in case no exceptions raise). So preparingTxs are never cleaned at all. Problem with txStores appears only with async mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-1077) Multiple leaves are not handled correctly with DIST

by Mircea Markus (JIRA)

Multiple leaves are not handled correctly with DIST ---------------------------------------------------- Key: ISPN-1077 URL: https://issues.jboss.org/browse/ISPN-1077 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.2.0.Final Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.2.2.FINAL, 5.0.0.FINAL When multiple caches are leaving at the same time(i.e. the diff between jgroups views is more than one address), Infinispan ends up with an inconsistent hash function: it is aware about nodes that are no longer present in the cluster. The root cause of the problem is in DistributionManagerImpl.rehash(...): - the list of leavers is determined as follows: Address leaver = MembershipArithmetic.getMemberLeft(oldMembers, newMembers); - this method always assumes a single leaver, but there can be many. Unit test attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2011