April 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3033) Lucene index stored in a StringBased CacheStore can get an unaligned bufferSize

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3033?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3033: ---------------------------------- Component/s: Lucene Directory > Lucene index stored in a StringBased CacheStore can get an unaligned bufferSize > ------------------------------------------------------------------------------- > > Key: ISPN-3033 > URL: https://issues.jboss.org/browse/ISPN-3033 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.0.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 5.3.0.CR1, 5.3.0.Final > > > In other words, the bufferSize is not loaded correctly from the key when using a org.infinispan.loaders.keymappers.TwoWayKey2StringMapper and this can lead to index corruption. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3033) Lucene index stored in a StringBased CacheStore can get an unaligned bufferSize

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3033?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3033: ---------------------------------- Labels: stable_embedded_query (was: ) > Lucene index stored in a StringBased CacheStore can get an unaligned bufferSize > ------------------------------------------------------------------------------- > > Key: ISPN-3033 > URL: https://issues.jboss.org/browse/ISPN-3033 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.0.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 5.3.0.CR1, 5.3.0.Final > > > In other words, the bufferSize is not loaded correctly from the key when using a org.infinispan.loaders.keymappers.TwoWayKey2StringMapper and this can lead to index corruption. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2957) CustomInterceptor configuration is incomplete and buggy

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2957?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reopened ISPN-2957: ----------------------------------- The commit caused regressions in Query: reopening > CustomInterceptor configuration is incomplete and buggy > ------------------------------------------------------- > > Key: ISPN-2957 > URL: https://issues.jboss.org/browse/ISPN-2957 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core API > Affects Versions: 5.2.1.Final > Reporter: Alan STS > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > Infinispan 5.2 schema allows to declare a custom interceptor with properties as follows: > <customInterceptors> > <interceptor position="LAST" class="com.group.awms.is.resource.dao.infinispan.interceptor.ApplicationInterceptor"> > <properties> > <property name="cacheActivityName" value="activity" /> > </properties> > </interceptor> > </customInterceptors> > Problem is that method parseInterceptor of class Parser52 does not expect any content for interceptors and the following exception is raised: > Message: Unexpected element '{urn:infinispan:config:5.2}properties' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:57) > at org.infinispan.configuration.parsing.ParseUtils.requireNoContent(ParseUtils.java:152) > at org.infinispan.configuration.parsing.Parser52.parseInterceptor(Parser52.java:1186) > at org.infinispan.configuration.parsing.Parser52.parseCustomInterceptors(Parser52.java:1148) > at org.infinispan.configuration.parsing.Parser52.parseCache(Parser52.java:156) > at org.infinispan.configuration.parsing.Parser52.parseNamedCache(Parser52.java:139) > at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:106) > at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:75) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:77) > ... 40 more > The Parser class is not in sync with the schema. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3022) Make CHMv8 the default CHM implementation when not running in Java8

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-3022?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-3022: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1777 > Make CHMv8 the default CHM implementation when not running in Java8 > ------------------------------------------------------------------- > > Key: ISPN-3022 > URL: https://issues.jboss.org/browse/ISPN-3022 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.2.5.Final > Reporter: Manik Surtani > Assignee: Manik Surtani > Labels: performance > Fix For: 5.3.0.Beta1, 5.3.0.Final > > > Our CHM implementation, backported from JDK 8, appears to be significantly faster and have a lower memory footprint. We should use this as the default CHM implementation. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2831) NPE in DistributedSegmentReadLocker

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2831?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-2831: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NPE in DistributedSegmentReadLocker > ----------------------------------- > > Key: ISPN-2831 > URL: https://issues.jboss.org/browse/ISPN-2831 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.1.Final, 5.3.0.Alpha1 > Reporter: Michal Zaborec > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 5.3.0.Beta1, 5.3.0.Final > > Attachments: unable-init-indexmanager-on-restart.txt > > > possible NPE in DistributedSegmentReadLocker > {code} > java.lang.NullPointerException > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.realFileDelete(DistributedSegmentReadLocker.java:184) > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(DistributedSegmentReadLocker.java:109) > at org.infinispan.lucene.InfinispanDirectory.deleteFile(InfinispanDirectory.java:213) > at org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:578) > {code} > this is caused by this code: > {code} > final int bufferSize = file.getBufferSize(); > if (file != null) //during optimization of index a same file could be deleted twice, so you could see a null here > ...... > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2831) NPE in DistributedSegmentReadLocker

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2831?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-2831: ---------------------------------- Labels: stable_embedded_query (was: ) > NPE in DistributedSegmentReadLocker > ----------------------------------- > > Key: ISPN-2831 > URL: https://issues.jboss.org/browse/ISPN-2831 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.1.Final, 5.3.0.Alpha1 > Reporter: Michal Zaborec > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 5.3.0.Beta1, 5.3.0.Final > > Attachments: unable-init-indexmanager-on-restart.txt > > > possible NPE in DistributedSegmentReadLocker > {code} > java.lang.NullPointerException > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.realFileDelete(DistributedSegmentReadLocker.java:184) > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(DistributedSegmentReadLocker.java:109) > at org.infinispan.lucene.InfinispanDirectory.deleteFile(InfinispanDirectory.java:213) > at org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:578) > {code} > this is caused by this code: > {code} > final int bufferSize = file.getBufferSize(); > if (file != null) //during optimization of index a same file could be deleted twice, so you could see a null here > ...... > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2831) NPE in DistributedSegmentReadLocker

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2831?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-2831: ---------------------------------- Fix Version/s: 5.3.0.Beta1 Component/s: Lucene Directory > NPE in DistributedSegmentReadLocker > ----------------------------------- > > Key: ISPN-2831 > URL: https://issues.jboss.org/browse/ISPN-2831 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.1.Final, 5.3.0.Alpha1 > Reporter: Michal Zaborec > Assignee: Sanne Grinovero > Fix For: 5.3.0.Beta1, 5.3.0.Final > > Attachments: unable-init-indexmanager-on-restart.txt > > > possible NPE in DistributedSegmentReadLocker > {code} > java.lang.NullPointerException > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.realFileDelete(DistributedSegmentReadLocker.java:184) > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(DistributedSegmentReadLocker.java:109) > at org.infinispan.lucene.InfinispanDirectory.deleteFile(InfinispanDirectory.java:213) > at org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:578) > {code} > this is caused by this code: > {code} > final int bufferSize = file.getBufferSize(); > if (file != null) //during optimization of index a same file could be deleted twice, so you could see a null here > ...... > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2957) CustomInterceptor configuration is incomplete and buggy

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2957?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-2957: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > CustomInterceptor configuration is incomplete and buggy > ------------------------------------------------------- > > Key: ISPN-2957 > URL: https://issues.jboss.org/browse/ISPN-2957 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core API > Affects Versions: 5.2.1.Final > Reporter: Alan STS > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > Infinispan 5.2 schema allows to declare a custom interceptor with properties as follows: > <customInterceptors> > <interceptor position="LAST" class="com.group.awms.is.resource.dao.infinispan.interceptor.ApplicationInterceptor"> > <properties> > <property name="cacheActivityName" value="activity" /> > </properties> > </interceptor> > </customInterceptors> > Problem is that method parseInterceptor of class Parser52 does not expect any content for interceptors and the following exception is raised: > Message: Unexpected element '{urn:infinispan:config:5.2}properties' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:57) > at org.infinispan.configuration.parsing.ParseUtils.requireNoContent(ParseUtils.java:152) > at org.infinispan.configuration.parsing.Parser52.parseInterceptor(Parser52.java:1186) > at org.infinispan.configuration.parsing.Parser52.parseCustomInterceptors(Parser52.java:1148) > at org.infinispan.configuration.parsing.Parser52.parseCache(Parser52.java:156) > at org.infinispan.configuration.parsing.Parser52.parseNamedCache(Parser52.java:139) > at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:106) > at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:75) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:77) > ... 40 more > The Parser class is not in sync with the schema. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2831) NPE in DistributedSegmentReadLocker

by Marko Lukša (JIRA)

[ https://issues.jboss.org/browse/ISPN-2831?page=com.atlassian.jira.plugin.... ] Marko Lukša updated ISPN-2831: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1776 I've also hit this today. I've moved the offending line inside the if statement. Pull request is at https://github.com/infinispan/infinispan/pull/1776 > NPE in DistributedSegmentReadLocker > ----------------------------------- > > Key: ISPN-2831 > URL: https://issues.jboss.org/browse/ISPN-2831 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.1.Final, 5.3.0.Alpha1 > Reporter: Michal Zaborec > Assignee: Sanne Grinovero > Fix For: 5.3.0.Final > > Attachments: unable-init-indexmanager-on-restart.txt > > > possible NPE in DistributedSegmentReadLocker > {code} > java.lang.NullPointerException > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.realFileDelete(DistributedSegmentReadLocker.java:184) > at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(DistributedSegmentReadLocker.java:109) > at org.infinispan.lucene.InfinispanDirectory.deleteFile(InfinispanDirectory.java:213) > at org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:578) > {code} > this is caused by this code: > {code} > final int bufferSize = file.getBufferSize(); > if (file != null) //during optimization of index a same file could be deleted twice, so you could see a null here > ...... > {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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3030) Implement a way to retrieve all keys from a REST endpoint

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-3030?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-3030: -------------------------------- It would be sufficient for me for this method to only return the keys local to that cache. As an additional option, perhaps it can also return *all* keys for that cache, similar to what is done in the HotRod client. The latter option would cause a distributed execution to fetch all keys, so would be relatively costly. The caller should be able to pick the option via a request header flag > Implement a way to retrieve all keys from a REST endpoint > --------------------------------------------------------- > > Key: ISPN-3030 > URL: https://issues.jboss.org/browse/ISPN-3030 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > The REST server should implement a method for handling GET /cacheName requests and return all available keys. > Depending on the "Accept" header, the keys may be returned in JSON, XML, HTML and plain text formats. -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2013