July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3147) Fix test ReplCommandForwardingTest.testForwardToJoinerNonTransactional

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3147?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3147: -------------------------------- Fix Version/s: 6.0.0.Final > Fix test ReplCommandForwardingTest.testForwardToJoinerNonTransactional > ---------------------------------------------------------------------- > > Key: ISPN-3147 > URL: https://issues.jboss.org/browse/ISPN-3147 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.3.0.CR1 > Reporter: Adrian Nistor > Assignee: Dan Berindei > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > This test is broken by ISPN-2772. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2971) AsyncStoreStressTest is broken

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2971?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2971: -------------------------------- Assignee: Galder Zamarreño (was: Adrian Nistor) > AsyncStoreStressTest is broken > ------------------------------ > > Key: ISPN-2971 > URL: https://issues.jboss.org/browse/ISPN-2971 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Galder Zamarreño > Labels: testsuite > Fix For: 6.0.0.Alpha1 > > > This test is not run during normal test suite, but we still need to fix this failure and the leaked threads (see System.exit(0) in main method): > {code} > testReadWriteRemove(org.infinispan.stress.AsyncStoreStressTest) Time elapsed: 72.377 sec <<< FAILURE! > java.lang.UnsupportedOperationException > at java.util.AbstractMap$SimpleImmutableEntry.setValue(AbstractMap.java:726) > at org.infinispan.stress.AsyncStoreStressTest.testReadWriteRemove(AsyncStoreStressTest.java:140) > 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) > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2771) WriteSkewTest.testWriteSkewWithOnlyPut fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2771?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2771: -------------------------------- Assignee: Pedro Ruivo (was: Adrian Nistor) > WriteSkewTest.testWriteSkewWithOnlyPut fails randomly > ----------------------------------------------------- > > Key: ISPN-2771 > URL: https://issues.jboss.org/browse/ISPN-2771 > Project: Infinispan > Issue Type: Bug > Components: Test Suite, Transactions > Affects Versions: 5.2.0.CR3 > Reporter: Adrian Nistor > Assignee: Pedro Ruivo > Fix For: 6.0.0.Alpha1 > > Attachments: WriteSkewTest.zip > > > {noformat} > org.infinispan.api.mvcc.repeatable_read.WriteSkewTest:testWriteSkewWithOnlyPut > org.infinispan.transaction.WriteSkewException: Detected write skew. > java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest.testWriteSkewWithOnlyPut(WriteSkewTest.java:315) > 22 lines not shown > Caused by Detected write skew. > org.infinispan.container.entries.RepeatableReadEntry.performLocalWriteSkewCheck(RepeatableReadEntry.java:68) > at org.infinispan.container.entries.RepeatableReadEntry.copyForUpdate(RepeatableReadEntry.java:52) > at org.infinispan.container.EntryFactoryImpl.wrapEntryForPut(EntryFactoryImpl.java:170) > at org.infinispan.interceptors.EntryWrappingInterceptor.visitPutKeyValueCommand(EntryWrappingInterceptor.java:164) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPutKeyValueCommand(OptimisticLockingInterceptor.java:142) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132) > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:251) > at org.infinispan.interceptors.TxInterceptor.visitPutKeyValueCommand(TxInterceptor.java:191) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:128) > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:92) > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:343) > at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1162) > at org.infinispan.CacheImpl.putInternal(CacheImpl.java:760) > at org.infinispan.CacheImpl.put(CacheImpl.java:754) > at org.infinispan.CacheImpl.put(CacheImpl.java:748) > at org.infinispan.CacheSupport.put(CacheSupport.java:53) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest$EntryWriter.call(WriteSkewTest.java:433) > at org.infinispan.api.mvcc.repeatable_read.WriteSkewTest$EntryWriter.call(WriteSkewTest.java:418) > 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) > 1 lines not shown > {noformat} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2958) Lucene Directory Read past EOF

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2958?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2958: -------------------------------- Assignee: Sanne Grinovero (was: Adrian Nistor) > Lucene Directory Read past EOF > ------------------------------ > > Key: ISPN-2958 > URL: https://issues.jboss.org/browse/ISPN-2958 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.1.Final > Reporter: Clement Pang > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > This seems to be happening rather deterministically. > Infinispan configuration (in JBoss EAP 6.1.0.Alpha): > {code} > <cache-container name="lucene"> > <local-cache name="dshell-index-data" start="EAGER"> > <eviction strategy="LIRS" max-entries="50000"/> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > <local-cache name="dshell-index-metadata" start="EAGER"> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > <local-cache name="dshell-index-lock" start="EAGER"> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > </cache-container> > {code} > Upon shutting down the server and confirming that passivation did indeed write the data to disk, the subsequent start-up would fail right away with: > {code} > Caused by: org.hibernate.search.SearchException: Could not initialize index > at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:162) > at org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider.start(InfinispanDirectoryProvider.java:103) > at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:104) > at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:227) > ... 64 more > Caused by: java.io.IOException: Read past EOF > at org.infinispan.lucene.SingleChunkIndexInput.readByte(SingleChunkIndexInput.java:77) > at org.apache.lucene.store.ChecksumIndexInput.readByte(ChecksumIndexInput.java:41) > at org.apache.lucene.store.DataInput.readInt(DataInput.java:86) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:272) > at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:182) > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1168) > at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:157) > ... 67 more > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2250) Handle all the remaining review comments for the NBST pull reques

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2250?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2250. --------------------------------- Resolution: Out of Date > Handle all the remaining review comments for the NBST pull reques > ----------------------------------------------------------------- > > Key: ISPN-2250 > URL: https://issues.jboss.org/browse/ISPN-2250 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Alpha3 > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha1 > > > These are still visible even after the pull request is closed. > Dan, please don't delete the t_nbst branch before handling these as we might loose them. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2608) VersionedDistStateTransferTest intermittent failure

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2608?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2608: -------------------------------- Assignee: Dan Berindei (was: Adrian Nistor) > VersionedDistStateTransferTest intermittent failure > --------------------------------------------------- > > Key: ISPN-2608 > URL: https://issues.jboss.org/browse/ISPN-2608 > Project: Infinispan > Issue Type: Bug > Components: State transfer, Test Suite > Affects Versions: 5.2.0.Beta5 > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > Attachments: vdstt.log.gz > > > Failure: > {quote} > org.infinispan.CacheException: Could not commit implicit transaction > at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1168) > at org.infinispan.CacheImpl.putInternal(CacheImpl.java:741) > at org.infinispan.CacheImpl.put(CacheImpl.java:735) > at org.infinispan.CacheImpl.put(CacheImpl.java:729) > at org.infinispan.CacheSupport.put(CacheSupport.java:53) > at org.infinispan.container.versioning.VersionedDistStateTransferTest.testStateTransfer(VersionedDistStateTransferTest.java:101) > 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: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: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:680) > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2515) org.infinispan.container.versioning.VersionedReplStateTransferTest.testStateTransfer fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2515?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2515: -------------------------------- Assignee: Dan Berindei (was: Adrian Nistor) > org.infinispan.container.versioning.VersionedReplStateTransferTest.testStateTransfer fails randomly > --------------------------------------------------------------------------------------------------- > > Key: ISPN-2515 > URL: https://issues.jboss.org/browse/ISPN-2515 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > Attachments: VersionedReplStateTransferTest_recent.log > > > The tests are failing during running testsuite for JDG. > You can find the logs here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > The bug doesn't appear if the test is run separately. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2515) org.infinispan.container.versioning.VersionedReplStateTransferTest.testStateTransfer fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2515?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2515: -------------------------------- Fix Version/s: 6.0.0.Final > org.infinispan.container.versioning.VersionedReplStateTransferTest.testStateTransfer fails randomly > --------------------------------------------------------------------------------------------------- > > Key: ISPN-2515 > URL: https://issues.jboss.org/browse/ISPN-2515 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > Attachments: VersionedReplStateTransferTest_recent.log > > > The tests are failing during running testsuite for JDG. > You can find the logs here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > The bug doesn't appear if the test is run separately. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2103) Concurrent access after removal of an AtomicMap should NOT result in an IllegalStateException when accessed by other threads

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2103?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2103: -------------------------------- Assignee: Galder Zamarreño (was: Adrian Nistor) > Concurrent access after removal of an AtomicMap should NOT result in an IllegalStateException when accessed by other threads > ---------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2103 > URL: https://issues.jboss.org/browse/ISPN-2103 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.1.5.FINAL > Reporter: Adrian Nistor > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > ISPN-1121 introduces an IllegalStateException that is being thrown from AtomicMap methods once the map handle has become stale (ie. removed from cache). In case of concurrent access, the exception is thrown to all threads not just to the thread that performed the removal. This was fine-ish in older versions of Infinispan before introduction of optimistic and pessimistic locking but it should be reconsidered now because: > 1. It interferes/overlaps with transaction isolation. We should rely on the selected locking scheme (OL/PL) to detect conflicts between transactions and report the problem accordingly. Especially if the stale map is used just for reading - this should be allowed to work rather than stop it. > 2. This exception is pretty disruptive and awkward to handle. All methods of an AtomicMap can result in this exception and the current thread has to be prepared for handling it if other threads remove the map. Not much transaction isolation. > 3. Since the TreeCache is backed by AtomicMap nearly all Tree API can throw this. > The proposed fix consists of: > 1. removing AtomicHashMap.removed flag and AtomicHashMap.markRemoved() method. > 2. revising AtomicHashMapProxy.assertValid() method to check only if the map is null (ie. removed) but no longer use the removed flag. > 3. revising ReadCommittedEntry.commit() method to no longer call markRemoved() method. > The consequences of these changes are: > 1. Any further access to a stale map results in IllegalStateException ONLY in the thread that performed the removal. This thread 'knows' the map is stale so it is fine to punish it. Other threads remain unaffected until lock acquisition or commit is performed (depending on locking model). > 2. Other threads can continue to use the previously obtained map handle for reads without danger of getting an exception. > 3. If a write operation is done on the map, the results depend on the locking model: > 3.1 optimistic locking + write skew check: a WriteSkewException will stop the commit during prepare > 3.2 optimistic locking, no write skew check: the write is committed and the work of the transaction that removed the map is overwritten. The map is effectively revived. > 3.3 pessimistic locking: same as 3.2 > Please note 3.2 and 3.3 work the same as for normal values (not atomic maps). -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2929) Fix quickstart license and white space issues exposed by qstool report

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2929?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2929: -------------------------------- Assignee: Pedro Ruivo (was: Mircea Markus) > Fix quickstart license and white space issues exposed by qstool report > ---------------------------------------------------------------------- > > Key: ISPN-2929 > URL: https://issues.jboss.org/browse/ISPN-2929 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Pedro Ruivo > Priority: Minor > Fix For: 6.0.0.Final > > > As a result of the face-to-face discussion on how to keep the quickstarts consistent and make maintenance less error-prone, Rafael has created a tool to automate this process. > Rafael updated all files with the correct license information as part of this commit: https://github.com/jboss-jdf/jboss-as-quickstart/commit/c6dc9668e7ce63861... > I have submitted a pull to correct most of the whitespace and tab issues: > https://github.com/jboss-jdf/jboss-as-quickstart/pull/474 > You need to fix these issues upstream. > You can find information about how to use Rafael's tool on the bottom of the page under "How to use Rafael's Tool" here: > https://docspace.corp.redhat.com/docs/DOC-132902 -- 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013