October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3584) JGroups subsystem XSD erroneously forgets about <relay> properties

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3584?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3584: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JGroups subsystem XSD erroneously forgets about <relay> properties > ------------------------------------------------------------------ > > Key: ISPN-3584 > URL: https://issues.jboss.org/browse/ISPN-3584 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.CR1 > > -- 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, 6 months

1
0
0 / 0

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

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3585: ------------------------------------- Summary: 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 Fix For: 6.0.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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3443) WriteCommand may be ignored during state transfer

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3443?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3443: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > WriteCommand may be ignored during state transfer > ------------------------------------------------- > > Key: ISPN-3443 > URL: https://issues.jboss.org/browse/ISPN-3443 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency, State transfer > Affects Versions: 6.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Blocker > Labels: jdg62blocker > Fix For: 6.0.0.CR1 > > > Distributed sync non-tx cache. > Situation: > 1) A node is joining the cluster, requesting some segment > 2) RemoveCommand is sent to backup owner with ignorePreviousValue=true > 3) It looks up the entry and finds null > 4) State transfer invokes the PutKeyValueCommand and sets the value for removed entry (updateKeys has not the key yet) > 5) RemoveCommand adds its key to updateKeys set, but it does not remove the value as it is already null (in its context) > Result: the value is removed on primary but on backup this is still present -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3583) When indexing is enabled but Query module isn't available configuration validation should fail

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3583?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3583: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 6.0.0.Final Resolution: Done > When indexing is enabled but Query module isn't available configuration validation should fail > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3583 > URL: https://issues.jboss.org/browse/ISPN-3583 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 6.0.0.CR1, 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3443) WriteCommand may be ignored during state transfer

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3443?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3443: ------------------------------- Priority: Blocker (was: Critical) > WriteCommand may be ignored during state transfer > ------------------------------------------------- > > Key: ISPN-3443 > URL: https://issues.jboss.org/browse/ISPN-3443 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency, State transfer > Affects Versions: 6.0.0.Alpha3 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Blocker > Labels: jdg62blocker > Fix For: 6.0.0.CR1 > > > Distributed sync non-tx cache. > Situation: > 1) A node is joining the cluster, requesting some segment > 2) RemoveCommand is sent to backup owner with ignorePreviousValue=true > 3) It looks up the entry and finds null > 4) State transfer invokes the PutKeyValueCommand and sets the value for removed entry (updateKeys has not the key yet) > 5) RemoveCommand adds its key to updateKeys set, but it does not remove the value as it is already null (in its context) > Result: the value is removed on primary but on backup this is still present -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2797) Support Query on Caches configured with INVALIDATION mode

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2797?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2797: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support Query on Caches configured with INVALIDATION mode > --------------------------------------------------------- > > Key: ISPN-2797 > URL: https://issues.jboss.org/browse/ISPN-2797 > Project: Infinispan > Issue Type: Feature Request > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: retest, stable_embedded_query > Fix For: 6.0.0.CR1, 6.0.0.Final > > > This is currently not supported as other nodes won't get a copy of the value, and are consequentially unable to scan annotations or recognize new services which need to be started. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3010) Cache GET operation retrieves a Class instance instead of expected type

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3010?page=com.atlassian.jira.plugin.... ] Pedro Ruivo resolved ISPN-3010. ------------------------------- Resolution: Out of Date it has not failed recently... If needed, it will be reopened > Cache GET operation retrieves a Class instance instead of expected type > ----------------------------------------------------------------------- > > Key: ISPN-3010 > URL: https://issues.jboss.org/browse/ISPN-3010 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.5.Final > Reporter: Sanne Grinovero > Assignee: Pedro Ruivo > Labels: retest, stable_embedded_query > Fix For: 6.0.0.CR1 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/hibernate-search-mast... > {quote} > Error Message > HSEARCH000103: Unable to initialize IndexManager emails > Stacktrace > org.hibernate.search.SearchException: HSEARCH000103: Unable to initialize IndexManager emails > at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:230) > at org.hibernate.search.indexes.impl.IndexManagerHolder.buildEntityIndexBinding(IndexManagerHolder.java:102) > at org.hibernate.search.spi.SearchFactoryBuilder.initDocumentBuilders(SearchFactoryBuilder.java:414) > at org.hibernate.search.spi.SearchFactoryBuilder.buildNewSearchFactory(SearchFactoryBuilder.java:222) > at org.hibernate.search.spi.SearchFactoryBuilder.buildSearchFactory(SearchFactoryBuilder.java:146) > at org.hibernate.search.event.impl.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:130) > at org.hibernate.search.hcore.impl.HibernateSearchIntegrator.integrate(HibernateSearchIntegrator.java:83) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:303) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1750) > at org.hibernate.search.test.util.FullTextSessionBuilder.build(FullTextSessionBuilder.java:182) > at org.hibernate.search.infinispan.StoredIndexTest.startNode(StoredIndexTest.java:121) > at org.hibernate.search.infinispan.StoredIndexTest.testRestartingNode(StoredIndexTest.java:53) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to [B > at org.infinispan.lucene.SingleChunkIndexInput.<init>(SingleChunkIndexInput.java:49) > at org.infinispan.lucene.InfinispanDirectory.openInput(InfinispanDirectory.java:290) > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:620) > 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.IndexReader.indexExists(IndexReader.java:1099) > at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:155) > 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) > ... 42 more > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3583) When indexing is enabled but Query module isn't available configuration validation should fail

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3583?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3583: ---------------------------------- Priority: Minor (was: Major) > When indexing is enabled but Query module isn't available configuration validation should fail > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3583 > URL: https://issues.jboss.org/browse/ISPN-3583 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 6.0.0.CR1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2797) Support Query on Caches configured with INVALIDATION mode

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2797?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-2797: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/infinispan/infinispan/pull/2135 (was: https://github.com/infinispan/infinispan/pull/2134) > Support Query on Caches configured with INVALIDATION mode > --------------------------------------------------------- > > Key: ISPN-2797 > URL: https://issues.jboss.org/browse/ISPN-2797 > Project: Infinispan > Issue Type: Feature Request > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: retest, stable_embedded_query > Fix For: 6.0.0.CR1, 6.0.0.Final > > > This is currently not supported as other nodes won't get a copy of the value, and are consequentially unable to scan annotations or recognize new services which need to be started. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3583) When indexing is enabled but Query module isn't available configuration validation should fail

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3583?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3583: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/infinispan/infinispan/pull/2135 (was: https://github.com/infinispan/infinispan/pull/2134) > When indexing is enabled but Query module isn't available configuration validation should fail > ---------------------------------------------------------------------------------------------- > > Key: ISPN-3583 > URL: https://issues.jboss.org/browse/ISPN-3583 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.0.0.CR1 > > -- 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, 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 2013