November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3667) Existing cacher stores should be generic types

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3667?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3667: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Existing cacher stores should be generic types > ---------------------------------------------- > > Key: ISPN-3667 > URL: https://issues.jboss.org/browse/ISPN-3667 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.CR1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: dm > Fix For: 6.1.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3524) Add RHQ support for registering protobuf descriptors

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3524?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3524: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Add RHQ support for registering protobuf descriptors > ---------------------------------------------------- > > Key: ISPN-3524 > URL: https://issues.jboss.org/browse/ISPN-3524 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 6.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 6.1.0.Final > > > This is the RHQ counterpart of ISPN-3172. -- 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-3669) Upgrade infinispan quickstarts to work with ISPN 6.0

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3669?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3669: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Upgrade infinispan quickstarts to work with ISPN 6.0 > ---------------------------------------------------- > > Key: ISPN-3669 > URL: https://issues.jboss.org/browse/ISPN-3669 > Project: Infinispan > Issue Type: Task > Reporter: Martin Gencur > Assignee: Pedro Ruivo > Priority: Blocker > Labels: 620 > Fix For: 6.1.0.Final > > > The infinispan-quickstart (https://github.com/infinispan/infinispan-quickstart) should be up-to-date for ISPN 6.0. > Also because Getting started guide is referring to them quite a lot. -- 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-3612) JON server plugin, unreachable NaN cache statistics values, even after Get Live Value

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3612?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3612: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > JON server plugin, unreachable NaN cache statistics values, even after Get Live Value > ------------------------------------------------------------------------------------- > > Key: ISPN-3612 > URL: https://issues.jboss.org/browse/ISPN-3612 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: William Burns > Priority: Critical > Labels: 620 > Fix For: 6.1.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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3585) The CDI module dependency on core and hotrod client should be optional

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3585?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3585: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > The CDI module dependency on core and hotrod client should be optional > ---------------------------------------------------------------------- > > Key: ISPN-3585 > URL: https://issues.jboss.org/browse/ISPN-3585 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Affects Versions: 6.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Labels: dm > Fix For: 6.1.0.Final > > > The CDI module Extension has a hard dependency on both core and remote. We need to refactor the code so that the two dependencies are optional and features are enabled only when found in classpath -- 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-3622) Configuration schema is not published at documented URL

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3622?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3622: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Configuration schema is not published at documented URL > ------------------------------------------------------- > > Key: ISPN-3622 > URL: https://issues.jboss.org/browse/ISPN-3622 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Documentation > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Priority: Critical > Fix For: 6.1.0.Final > > > Some examples refer to URL http://www.infinispan.org/schemas/infinispan-config-6.0.xsd to find the XSD, but it's not there. > This combined with the missing documentation makes it quite a guesswork on how to configure it. -- 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-3659) Cache stop should clear thread-local ExtendedRiverMarshaller or their instance caches

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3659?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3659: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Cache stop should clear thread-local ExtendedRiverMarshaller or their instance caches > ------------------------------------------------------------------------------------- > > Key: ISPN-3659 > URL: https://issues.jboss.org/browse/ISPN-3659 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 5.3.0.Final, 6.0.0.CR1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > > The fix for ISPN-2372 was incomplete. We now clear the references from the thread-local marshallers to the cache itself, so it can be garbage-collected, but we don't clear the marshallers or their instance caches. If the cache values' object graph is very large, the cached marshallers will use up a lot of memory that could be garbage-collected (assuming the cache was indeed restarted and only one cache instance is running now). -- 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-3184) The DELTA_WRITE flag should force a remote get during state transfer

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3184?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3184: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > The DELTA_WRITE flag should force a remote get during state transfer > -------------------------------------------------------------------- > > Key: ISPN-3184 > URL: https://issues.jboss.org/browse/ISPN-3184 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > > AtomicHashMap and FineGrainedAtomicHashMap, as well as custom DeltaAware implementations, use PutKeyValueCommands with the DELTA_WRITE flag to execute incremental updates. These commands need the previous value of the entry in order to work. > If a node is joining and it receives a PutKeyValueCommand with the DELTA_WRITE flag before it has received the value of the affected key, it should do a remote get to retrieve the previous value and apply the change on top of that value, just like we do for conditional commands. Not doing so leads to data loss. -- 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-3432) Data put to index enabled cache with Infinispan Directory provider using Async. JDBC StringBased CacheStore fails

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3432?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3432: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Data put to index enabled cache with Infinispan Directory provider using Async. JDBC StringBased CacheStore fails > ----------------------------------------------------------------------------------------------------------------- > > Key: ISPN-3432 > URL: https://issues.jboss.org/browse/ISPN-3432 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 6.0.0.Alpha1 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Priority: Critical > Labels: 620 > Fix For: 6.1.0.Final > > Attachments: async-config.xml > > > Hi, > this issue is related to the ISPN-3090, but I thought to specify this case separately for bringing detailed explanation for the configuration and thrown exceptions. > The issue relates to the performance tests for Index enabled Infinispan cache, with configured Infinispan directory and Async JDBC. String Based Cache store. > The tests are running on 4 nodes and performing puts/gets on all nodes with many threads. > The problem is that, during data put, the following exceptions are thrown continuously: > {code} > 04:04:05,633 ERROR [org.hibernate.search.exception.impl.LogErrorHandler] (Hibernate Search: Index updates queue processor for index query-1) HSEARCH000058: Exception occurred org.apache.lucene.index.IndexNotFoundException: no segments* file found in InfinispanDirectory{indexName='query'}: files: [] > Primary Failure: > Entity org.radargun.cachewrappers.InfinispanQueryWrapper$QueryableData Id S:_InstallBenchmarkStage_0 Work Type org.hibernate.search.backend.UpdateLuceneWork > org.apache.lucene.index.IndexNotFoundException: no segments* file found in InfinispanDirectory{indexName='query'}: files: [] > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:667) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:554) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359) > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1138) > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.createNewIndexWriter(IndexWriterHolder.java:148) > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.getIndexWriter(IndexWriterHolder.java:115) > at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriter(AbstractWorkspaceImpl.java:117) > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:101) > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:67) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > 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:724) > ...... > 04:14:21,605 ERROR [org.hibernate.search.exception.impl.LogErrorHandler] (Hibernate Search: Index updates queue processor for index query-1) HSEARCH000058: Exception occurred org.apache.lucene.index.IndexNotFoundException: no segments* file found in InfinispanDirectory{indexName='query'}: files: [] > Primary Failure: > Entity org.radargun.cachewrappers.InfinispanQueryWrapper$QueryableData Id S:key_0_0_0000000000000017 Work Type org.hibernate.search.backend.UpdateLuceneWork > org.apache.lucene.index.IndexNotFoundException: no segments* file found in InfinispanDirectory{indexName='query'}: files: [] > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:667) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:554) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359) > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1138) > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.createNewIndexWriter(IndexWriterHolder.java:148) > at org.hibernate.search.backend.impl.lucene.IndexWriterHolder.getIndexWriter(IndexWriterHolder.java:115) > at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriter(AbstractWorkspaceImpl.java:117) > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:101) > at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:67) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > 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:724) > {code} > You can find the cache configuration attached. > Yet another thing to mention: > if the following line is added to the cache configuration: > {code} > <property name="default.indexmanager" value="org.infinispan.query.indexmanager.InfinispanIndexManager" /> > {code} > then the issue is gone - no lock issue appears then. -- 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-3638) Upgrade to JGroups 3.4.0.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3638?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3638: -------------------------------- Fix Version/s: 6.1.0.Final (was: 6.0.0.Final) > Upgrade to JGroups 3.4.0.Final > ------------------------------ > > Key: ISPN-3638 > URL: https://issues.jboss.org/browse/ISPN-3638 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 6.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.1.0.Final > > > The fix for JGRP-1675 should be useful when we run out of OOB threads (REPLENISH messages are now flagged as INTERNAL). -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2013