October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4601) DirectoryLoaderAdaptor computes the auto-chunk factor applying wrong rounding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4601: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139645|https://bugzilla.redhat.com/show_bug.cgi?id=1139645] from ON_QA to VERIFIED > DirectoryLoaderAdaptor computes the auto-chunk factor applying wrong rounding > ----------------------------------------------------------------------------- > > Key: ISPN-4601 > URL: https://issues.jboss.org/browse/ISPN-4601 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.Beta1 > > > Better described by the patch. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2932) Preloading a read only index in a cache will never hit the cacheloader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2932?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2932: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139645|https://bugzilla.redhat.com/show_bug.cgi?id=1139645] from ON_QA to VERIFIED > Preloading a read only index in a cache will never hit the cacheloader > ---------------------------------------------------------------------- > > Key: ISPN-2932 > URL: https://issues.jboss.org/browse/ISPN-2932 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta1 > > > With a warm cache (with no eviction) we should never need to hit the CacheLoader again. > Was reported - specifically with DIST on multiple nodes - that occasionall IO is triggered; we should add tests to verify this doesn't happen (or to understand why it should) > I'm suspecting demand of null valued entries. > mailing list thread: http://lists.jboss.org/pipermail/infinispan-dev/2013-March/012261.html -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4605) Race condition during Marshalling of Lucene Directory components would trigger nonsense during unmarshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4605?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4605: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139651|https://bugzilla.redhat.com/show_bug.cgi?id=1139651] from ON_QA to VERIFIED > Race condition during Marshalling of Lucene Directory components would trigger nonsense during unmarshalling > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-4605 > URL: https://issues.jboss.org/browse/ISPN-4605 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 7.0.0.Alpha5 > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.Beta1 > > > Some components in the Lucene Directory are highly concurrent, when these are marshalled we need to ensure a consistent snapshot is written to the byte stream. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3329) DatabaseStoredIndexTest.indexWasStored random failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3329?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3329: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139651|https://bugzilla.redhat.com/show_bug.cgi?id=1139651] from ON_QA to VERIFIED > DatabaseStoredIndexTest.indexWasStored random failures > ------------------------------------------------------ > > Key: ISPN-3329 > URL: https://issues.jboss.org/browse/ISPN-3329 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 6.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Sanne Grinovero > Labels: testsuite_stability > Fix For: 7.0.0.Beta1 > > > The test fails quite often with an assertion error like this: > {noformat} > java.lang.AssertionError: > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) > at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:41) > at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:49) > at org.infinispan.lucene.DatabaseStoredIndexTest.indexWasStored(DatabaseStoredIndexTest.java:111) > ------- Stdout: ------- > Failure on key[_0.nrm|0|16384|testing index] expected value: > ByteArray{size=6, array=0x4e524dff7c79..} actual value: > null > {noformat} > See http://ci.infinispan.org/project.html?projectId=Infinispan&tab=testDetail... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4498) OutOfMemoryError when CI is ran with tracing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4498?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4498: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139642|https://bugzilla.redhat.com/show_bug.cgi?id=1139642] from ON_QA to VERIFIED > OutOfMemoryError when CI is ran with tracing > -------------------------------------------- > > Key: ISPN-4498 > URL: https://issues.jboss.org/browse/ISPN-4498 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5 > > > The CI will fail very often when tracing is enabled with some sort of OOM error. > http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_MasterHotsp... > Looking closer this appears to be an issue with an accumulation of Threads. These threads aren't running either but rather are held in memory unneedingly. It appears that they are being retained in the log4j1.2 NDC class in it's hashtable. Upon further investigation we never call to NDC.remove which would clear up the current any dead threads. > I have created JBLOGGING-106 to fix this as well. In the mean time we shouldn't use NDC. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4643) Make sure EntryIterator doesn't return expired entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4643?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-4643: ----------------------------------- Assignee: William Burns (was: Dan Berindei) > Make sure EntryIterator doesn't return expired entries > ------------------------------------------------------ > > Key: ISPN-4643 > URL: https://issues.jboss.org/browse/ISPN-4643 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR2 > > > We should make sure that the entry iterator doesn't return entries that have expired. Since entries can sit in the data container while expired we need to make sure to ignore those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4643) Make sure EntryIterator doesn't return expired entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4643?page=com.atlassian.jira.plugin.... ] Work on ISPN-4643 started by William Burns. ------------------------------------------- > Make sure EntryIterator doesn't return expired entries > ------------------------------------------------------ > > Key: ISPN-4643 > URL: https://issues.jboss.org/browse/ISPN-4643 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR2 > > > We should make sure that the entry iterator doesn't return entries that have expired. Since entries can sit in the data container while expired we need to make sure to ignore those. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4640) Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4640?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4640: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139631|https://bugzilla.redhat.com/show_bug.cgi?id=1139631] from ON_QA to VERIFIED > Enhance distributed iterator to allow filter and converter to be executed in the same step/invocation > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-4640 > URL: https://issues.jboss.org/browse/ISPN-4640 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.0.0.Beta2 > > > This enhancement is needed for performance and should make FilterAndConverter class obsolete. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4654) AND over range queries does not work (indexless query)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4654?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4654: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139650|https://bugzilla.redhat.com/show_bug.cgi?id=1139650] from ON_QA to VERIFIED > AND over range queries does not work (indexless query) > ------------------------------------------------------ > > Key: ISPN-4654 > URL: https://issues.jboss.org/browse/ISPN-4654 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta2 > > > Check this in QueryDslConditionsTest: > {code} > public void testAnd5() throws Exception { > QueryFactory qf = getQueryFactory(); > // range queries use different code > Query q = qf.from(getModelFactory().getUserImplClass()) > .having("id").lt(1000) > .and().having("age").lt(1000) > .toBuilder().build(); > List<User> list = q.list(); > assertEquals(3, list.size()); > } > {code} > The problem is that some subscription gets suspended and the second LT does not fire the second predicate update (and then neither the AND reevaluation). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4604) Race condition in the QueryInterceptor involving SearchFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4604?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4604: ----------------------------------------------- Jakub Markos <jmarkos(a)redhat.com> changed the Status of [bug 1139669|https://bugzilla.redhat.com/show_bug.cgi?id=1139669] from ON_QA to VERIFIED > Race condition in the QueryInterceptor involving SearchFactory > -------------------------------------------------------------- > > Key: ISPN-4604 > URL: https://issues.jboss.org/browse/ISPN-4604 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Test Suite - Query > Affects Versions: 7.0.0.Alpha5 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.0.0.Beta1 > > > During perform work task in the QueryInterceptor, the underlying SearchFactory could be swapped (for example by some other thread calling SearchFactory.addClass) and temporarily return null when looking for indexBindings, and throws intermittent Exceptions like: > {code} > Caused by: org.hibernate.search.exception.SearchException: Unable to perform work. Entity Class is not @Indexed nor hosts @ContainedIn: class org.infinispan.query.test.VeryLongIndexNamedClass > at org.hibernate.search.backend.impl.TransactionalWorker.performWork(TransactionalWorker.java:58) > at org.infinispan.query.backend.QueryInterceptor.performSearchWorks(QueryInterceptor.java:233) > at org.infinispan.query.backend.QueryInterceptor.performSearchWork(QueryInterceptor.java:227) > at org.infinispan.query.backend.QueryInterceptor.updateIndexes(QueryInterceptor.java:221) > at org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(QueryInterceptor.java:531) > at org.infinispan.query.backend.QueryInterceptor.visitPutKeyValueCommand(QueryInterceptor.java:162) > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:71) > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) > at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitPutKeyValueCommand(AbstractLockingInterceptor.java:46) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014