May 2011 - infinispan-issues - Jboss List Archives

[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

12 years, 11 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

12 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-909) Segments locked during merge

by Tristan Tarrant (JIRA)

Segments locked during merge ---------------------------- Key: ISPN-909 URL: https://issues.jboss.org/browse/ISPN-909 Project: Infinispan Issue Type: Bug Components: Lucene Directory Affects Versions: 4.2.0.Final Reporter: Tristan Tarrant Assignee: Sanne Grinovero Attachments: rabbit-1-mergelock.log, rabbit-2-mergelock.log We're getting failures on acquiring locks during merges. Here is the configuration: Infinispan: 3 caches: lockCache (replicated, volatile, no eviction), metadataCache (replicated, persisted, no eviction), dataCache (distributed, persisted, eviction). Node 1: coordinator, IndexWriter open constantly and writing a stream of documents Node 2: opens a read-only IndexReader on-demand to perform queries (we're moving to use IndexReader.reopen() ). Occasionally when performing queries on node 2 we get the attached stack traces. We then get corrupt indexes (java.io.IOException: Read past EOF). We are using the default Distributed Segment Lock Reader, default 16K chunks and no tuning of the merge policies. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-1087) QueryFactory Object does not exist

by Jeff LaFrate (JIRA)

QueryFactory Object does not exist ---------------------------------- Key: ISPN-1087 URL: https://issues.jboss.org/browse/ISPN-1087 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.CR1 Environment: Infinispan infinispan-5.0.0.CR1-bin.zip Reporter: Jeff LaFrate Assignee: Manik Surtani I am trying to query the infinispan cache using your documentation at http://community.jboss.org/wiki/QueryingInfinispan/diff?secondVersionNumb... See section "usage with Infinispan 5": When using Infinispan 5, it's a bit simpler: you don't need the QueryHelper, and just create a QueryFactory directly from the cache: QueryFactory qf = new QueryFactory(cache); CacheQuery cacheQuery = qf.getQuery( any org.apache.lucene.search.Query ); List<Object> found = cacheQuery.list(); Problem: org.infinispan.query.QueryFactory; does not exist in infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. Thoughts. Thanks Jeff -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-1138) Double override of BooleanAttributeType doesn't work

by Paul Ferraro (JIRA)

Double override of BooleanAttributeType doesn't work ---------------------------------------------------- Key: ISPN-1138 URL: https://issues.jboss.org/browse/ISPN-1138 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.0.0.CR3 Reporter: Paul Ferraro Assignee: Galder Zamarreño The following test fails on the last assertion: @Test public void invocationBatching() { System.out.println(org.infinispan.Version.printVersion()); EmbeddedCacheManager manager = new DefaultCacheManager(new GlobalConfiguration(), new Configuration()); Configuration override = new Configuration(); override.fluent().invocationBatching(); assert override.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test1", override).isInvocationBatchingEnabled(); Configuration config = new Configuration(); config.applyOverrides(override); assert config.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test2", config).isInvocationBatchingEnabled(); } In the above code, the last assertion fails. If you modify the above code to test for isIndexingEnabled(), the same failure occurs. The problem is likely generalizable to all boolean configuration properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-1135) Fix issues reported by the Klockwork report (build_2011_5_16)

by Galder Zamarreño (JIRA)

Fix issues reported by the Klockwork report (build_2011_5_16) ------------------------------------------------------------- Key: ISPN-1135 URL: https://issues.jboss.org/browse/ISPN-1135 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR4 Summary of things to fix as a result of the Klockwork report: - DataContainerFactory: String comparison via == configuration.getDataContainerClass() == DefaultDataContainer.class.getName() More to come... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-1134) New JMX MBeans documentation

by Galder Zamarreño (JIRA)

New JMX MBeans documentation ---------------------------- Key: ISPN-1134 URL: https://issues.jboss.org/browse/ISPN-1134 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR4 Document the new Netty and JGroups JMX beans that are registered in Infinispan 5.0. Also verify that they get documented correctly in http://docs.jboss.org/infinispan/5.0/apidocs/jmxComponents.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-1142) reference to a non existing Maven repository

by Sanne Grinovero (JIRA)

reference to a non existing Maven repository -------------------------------------------- Key: ISPN-1142 URL: https://issues.jboss.org/browse/ISPN-1142 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.CR3 Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Blocker Fix For: 5.0.0.CR4 {quote}http://repository.jboss.org/maven2{quote} does not exist anymore, still the parent pom is referencing it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1139) Remove SLF4J from the project

by Sanne Grinovero (JIRA)

Remove SLF4J from the project ----------------------------- Key: ISPN-1139 URL: https://issues.jboss.org/browse/ISPN-1139 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Optional Fix For: 5.0.0.CR4 Some projects are still demanding slf4j on the classpath, while it's not being used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1122) InvalidResponseException when running ServerErrorTest from testsuite

by Galder Zamarreño (JIRA)

InvalidResponseException when running ServerErrorTest from testsuite -------------------------------------------------------------------- Key: ISPN-1122 URL: https://issues.jboss.org/browse/ISPN-1122 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR3 I've seen this in master, when running ServerErrorTest from testsuite: {code}[z@dnb-2:~/Go/code/infinispan.git]% (t_1119_m⚡) more client/hotrod-client/target/surefire-reports/TEST-org.infinispan.client.hotrod.ServerErrorTest-testErrorWhileDoingPut.xml <?xml version="1.0" encoding="UTF-8" ?> <testsuite time="0" name="org.infinispan.client.hotrod.ServerErrorTest-testErrorWhileDoingPut"> <testcase time="0.265" classname="org.infinispan.client.hotrod.ServerErrorTest" name="org.infinispan.client.hotrod.ServerErrorTest-testErrorWhileDoingPut"> <failure message="Invalid magic number. Expected 0xa1 and received 0x50" type="org.infinispan.client.hotrod.exceptions.InvalidResponseException">org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x50 at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:107) at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:70) at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:49) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:62) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:201) at org.infinispan.CacheSupport.put(CacheSupport.java:51) at org.infinispan.client.hotrod.ServerErrorTest.testErrorWhileDoingPut(ServerErrorTest.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeMethod(Invoker.java:546) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:909) at org.testng.TestRunner.privateRun(TestRunner.java:618) at org.testng.TestRunner.run(TestRunner.java:499) at org.testng.SuiteRunner.runTest(SuiteRunner.java:332) at org.testng.SuiteRunner.access$000(SuiteRunner.java:33) at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:358) at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:142) 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:680) </failure>{code} This needs investigate cos it could be related to other Invalid* issues QE have been encountering with EDG. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2011