August 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2475) When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2475?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2475: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners > ----------------------------------------------------------------------------------- > > Key: ISPN-2475 > URL: https://issues.jboss.org/browse/ISPN-2475 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.1.0.FINAL > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 6.0.0.Alpha3 > > > Copied from the parent: > {quote} > [...] we can keep track of the consistent hashes in the last 10 minutes (or whatever the L1 lifespan is) and the time of the last invalidation sent for each key. When we need to send a new invalidation, we add the owners in all the consistent hashes since the last invalidation to the invalidation command recipients. > {quote} -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2895) org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2895?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2895: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly > -------------------------------------------------------------------------------- > > Key: ISPN-2895 > URL: https://issues.jboss.org/browse/ISPN-2895 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.2.Final > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Labels: stable_embedded_query, testsuite_stability > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > The test fails randomly and the error message is: > {code} > java.lang.NullPointerException > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:76) > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:56) > at org.infinispan.lucene.InfinispanDirectoryIOTest.verifyOnBuffer(InfinispanDirectoryIOTest.java:184) > at org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile(InfinispanDirectoryIOTest.java:153) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2780) org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails randomly on all environments

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2780?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2780: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails randomly on all environments > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2780 > URL: https://issues.jboss.org/browse/ISPN-2780 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.0.CR3 > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > > The test org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest fails almost always on all environments. The error message is: > {code} > Error Message > String '0' should exist but was not found in index > Stacktrace > java.lang.AssertionError: String '0' should exist but was not found in index > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.verifyOnDirectory(IndexCacheLoaderTest.java:131) > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.verifyIndex(IndexCacheLoaderTest.java:83) > at org.infinispan.lucene.cacheloader.IndexCacheLoaderTest.readExistingIndexTest(IndexCacheLoaderTest.java:71) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2709) Lib dir in distribution archive does not contain the proper versions for some dependencies

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2709?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2709: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Lib dir in distribution archive does not contain the proper versions for some dependencies > ------------------------------------------------------------------------------------------- > > Key: ISPN-2709 > URL: https://issues.jboss.org/browse/ISPN-2709 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.CR1 > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > Attachments: actual.txt, should_be.txt > > > Not all the jars referenced by runtime-classpath.txt files of modules are actually present in the lib dir. In some cases the jar is present but not the needed version. Some of the jars are there but are not actually used. > It all happens because the set of dependencies for runtime-classpath.txt is computed for each individual module while the lib dir in the distro is created by assembly plugin after 'merging' the dependencies of all modules which means that only the highest version will be included. Also, maven dependency plugin is known to miss some dependencies. > To avoid the version problem we could define globally a single version for each of these dependencies in parent pom dependencyManagement and also explicitly add the dependency in the respective modules. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2965) L1 and early invalidation leaves inconsistent state

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2965?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2965: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > L1 and early invalidation leaves inconsistent state > --------------------------------------------------- > > Key: ISPN-2965 > URL: https://issues.jboss.org/browse/ISPN-2965 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache, Transactions > Affects Versions: 5.2.1.Final > Reporter: Sebastian Tusk > Assignee: William Burns > Labels: 5.2.x > Fix For: 6.0.0.Alpha3 > > > In a distributed transactional cache with L1 enabled I can observe the following. > Prepare cache by adding an entry with Cache.put( k, v1 ). > 1. Node B starts with adding a changed value. Cache.put( k, v2 ) > 2. Node B TxDistributionInterceptor.visitPrepareCommand flushL1Caches sends invalidations. > 3. Node A calls Cache.get( k ) retrieves v1 and stores this value in L1. > 4. Node B proceeds with transaction. > The result is that Node A answers subsequent Cache.get(k) with v1 and Node B answers with v2. > It seems the invalidation is either send to early or must be synchronized in some way with the transaction. > Cache config: > <namedCache name="entity"> > <jmxStatistics enabled="true" /> > <clustering mode="dist"> > <stateTransfer fetchInMemoryState="false" timeout="20000" /> > <async /> > <l1 enabled="true" /> > <hash numOwners="1"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" > lockAcquisitionTimeout="15000" useLockStriping="false" /> > <eviction maxEntries="10000" strategy="LRU" /> > <expiration maxIdle="100000" wakeUpInterval="5000"/> > <storeAsBinary storeKeysAsBinary="true" storeValuesAsBinary="false" enabled="false" /> > <transaction transactionMode="TRANSACTIONAL" autoCommit="false" lockingMode="OPTIMISTIC"/> > </namedCache> -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2930) ChainingCacheLoaderTest intermittent failure

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2930?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2930: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > ChainingCacheLoaderTest intermittent failure > -------------------------------------------- > > Key: ISPN-2930 > URL: https://issues.jboss.org/browse/ISPN-2930 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Test Suite > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > Attachments: ChainingCacheLoaderTest.log > > > Test fails sometimes. See attached log. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3047) Drop encoding from CLI once servers store raw values

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3047?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3047: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Drop encoding from CLI once servers store raw values > ---------------------------------------------------- > > Key: ISPN-3047 > URL: https://issues.jboss.org/browse/ISPN-3047 > Project: Infinispan > Issue Type: Task > Components: CLI > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3, 6.0.0.Final > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3045) Drop wrappers from RemoteCacheStore once HotRod server supports raw keys/values

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3045?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3045: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Drop wrappers from RemoteCacheStore once HotRod server supports raw keys/values > ------------------------------------------------------------------------------- > > Key: ISPN-3045 > URL: https://issues.jboss.org/browse/ISPN-3045 > Project: Infinispan > Issue Type: Task > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha3 > > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3037) Failing test: MixedModeTest.testMixedMode:72 NullPointer

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3037?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3037: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > Failing test: MixedModeTest.testMixedMode:72 NullPointer > -------------------------------------------------------- > > Key: ISPN-3037 > URL: https://issues.jboss.org/browse/ISPN-3037 > Project: Infinispan > Issue Type: Bug > Reporter: Sanne Grinovero > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 6.0.0.Alpha3 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~ > jgroups.bind_addr = 127.0.0.1 > java.runtime.version = 1.6.0_43-b01 > java.runtime.name =Java(TM) SE Runtime Environment > java.vm.version = 20.14-b01 > java.vm.vendor = Sun Microsystems Inc. > os.name = Linux > os.version = 3.8.8-202.fc18.x86_64 > sun.arch.data.model = 64 > sun.cpu.endian = little > protocol.stack = null > infinispan.test.jgroups.protocol = tcp > infinispan.unsafe.allow_jdk8_chm = true > java.net.preferIPv4Stack = true > java.net.preferIPv6Stack = null > log4.configuration = null > MAVEN_OPTS = null > ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~ > Tests run: 2911, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 212.448 sec <<< FAILURE! > testMixedMode(org.infinispan.api.MixedModeTest) Time elapsed: 0.03 sec <<< FAILURE! > java.lang.NullPointerException > at org.infinispan.api.MixedModeTest.testMixedMode(MixedModeTest.java:72) > 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.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Results : > Failed tests: > MixedModeTest.testMixedMode:72 NullPointer > Tests run: 2911, Failures: 1, Errors: 0, Skipped: 0 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2973) HotRod client doesn't retry on suspect

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2973?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2973: ------------------------------- Fix Version/s: 6.0.0.Alpha3 (was: 6.0.0.Alpha2) > HotRod client doesn't retry on suspect > -------------------------------------- > > Key: ISPN-2973 > URL: https://issues.jboss.org/browse/ISPN-2973 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.2.Final > Reporter: Takayoshi Kimura > Assignee: Tristan Tarrant > Fix For: 5.2.6.Final, 6.0.0.Alpha3 > > > HotRod client does retry on RemoteNodeSuspectException and Codec10#checkForErrorsInResponseStatus() checks message from server if it contains "Suspect" message. > ISPN-2737 fix changed the message and HotRod is unable to perform retry as there is no "Suspect" string in the message from server. > ISPN-2737 PullReq: https://github.com/infinispan/infinispan/pull/1629 and commit https://github.com/galderz/infinispan/commit/3ee1b96ace284ba108eb3abfd855... -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2013