January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3795) QueryInterceptor incorrectly relies on the return value of a RemoveCommand

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3795?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3795: ------------------------------------- Assignee: Sanne Grinovero > QueryInterceptor incorrectly relies on the return value of a RemoveCommand > -------------------------------------------------------------------------- > > Key: ISPN-3795 > URL: https://issues.jboss.org/browse/ISPN-3795 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Sanne Grinovero > > QueryInterceptor uses the return value from RemoveCommand/ReplaceCommand to remove the value from the index. > But both RemoveCommand and ReplaceCommand have a variant with an expected value parameter, and this variant return a boolean value instead of the removed/replaced value. In that case, the previous value won't be removed from the index. > QueryInterceptor should probably use the previous value from the context entries to update the index instead. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3790) Document the rules for handling null values in the Equivalence interface

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3790?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3790: ------------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > Document the rules for handling null values in the Equivalence interface > ------------------------------------------------------------------------ > > Key: ISPN-3790 > URL: https://issues.jboss.org/browse/ISPN-3790 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > > {{AnyEquivalence.equals(null, null)}} returns false, and {{ByteArrayEquivalence.equals(null, null)}} returns true. > I think ByteArrayEquivalence is correct, and the {{Equivalence.equals()}} javadoc should specify that two {{null}} values should be equal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3790) Document the rules for handling null values in the Equivalence interface

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3790?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3790: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Document the rules for handling null values in the Equivalence interface > ------------------------------------------------------------------------ > > Key: ISPN-3790 > URL: https://issues.jboss.org/browse/ISPN-3790 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > > {{AnyEquivalence.equals(null, null)}} returns false, and {{ByteArrayEquivalence.equals(null, null)}} returns true. > I think ByteArrayEquivalence is correct, and the {{Equivalence.equals()}} javadoc should specify that two {{null}} values should be equal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3823) Migrators should not pollute each other with their "global" key entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3823: ---------------------------------- Description: Migrators should use bulk retrieval methods instead of the global key entry strategy. Once we have distributed iterators for the remote protocols, implement migrators on top of them > Migrators should not pollute each other with their "global" key entries > ----------------------------------------------------------------------- > > Key: ISPN-3823 > URL: https://issues.jboss.org/browse/ISPN-3823 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > > Migrators should use bulk retrieval methods instead of the global key entry strategy. Once we have distributed iterators for the remote protocols, implement migrators on top of them -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3824) Upgrade to JBoss Transactions 4.17.29

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3824?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3824: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3202 > Upgrade to JBoss Transactions 4.17.29 > ------------------------------------- > > Key: ISPN-3824 > URL: https://issues.jboss.org/browse/ISPN-3824 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3823) Migrators should not pollute each other with their "global" key entries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3823: ---------------------------------- Fix Version/s: (was: 7.1.0.CR1) > Migrators should not pollute each other with their "global" key entries > ----------------------------------------------------------------------- > > Key: ISPN-3823 > URL: https://issues.jboss.org/browse/ISPN-3823 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Tristan Tarrant > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3824) Upgrade to JBoss Transactions 4.17.29

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3824?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3824: ---------------------------------- Summary: Upgrade to JBoss Transactions 4.17.29 (was: Upgrade to JBoss Transactions 4.17.20) > Upgrade to JBoss Transactions 4.17.29 > ------------------------------------- > > Key: ISPN-3824 > URL: https://issues.jboss.org/browse/ISPN-3824 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3824) Upgrade to JBoss Transactions 4.17.29

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3824?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3824: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > Upgrade to JBoss Transactions 4.17.29 > ------------------------------------- > > Key: ISPN-3824 > URL: https://issues.jboss.org/browse/ISPN-3824 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 7.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3854) Tests from org.infinispan.eviction package fail randomly with Oracle JDK and constantly with IBM JDK6

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3854?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3854: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Final (was: 7.1.0.CR1) Resolution: Done > Tests from org.infinispan.eviction package fail randomly with Oracle JDK and constantly with IBM JDK6 > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-3854 > URL: https://issues.jboss.org/browse/ISPN-3854 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Reporter: Vitalii Chepeliuk > Assignee: Pedro Ruivo > Priority: Critical > Labels: testsuite_stability > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > Attachments: EvictionWithPassivationAndConcurrentOperationsTest.log.zip, ManualEvictionWithPassivationAndConcurrentOperationsInPrimaryOwnerTest.log.zip > > > Following tests fail randomly on JDK7 > org.infinispan.eviction.ManualEvictionWithPassivationAndConcurrentOperationsInPrimaryOwnerTest.testScenario6 > org.infinispan.eviction.EvictionWithPassivationAndConcurrentOperationsTest.testScenario6 > OracleJDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > IBM7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > OpenJDK7 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > And bunch of tests fail on IBM6 > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > and here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Add windows runs > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3866) Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3866?page=com.atlassian.jira.plugin.... ] Tristan Tarrant resolved ISPN-3866. ----------------------------------- Fix Version/s: 7.0.0.Final (was: 7.1.0.CR1) Resolution: Done > Parser60.parseStore() ignores store configurations if they are not a SingleFileStore or a ClusterLoader > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-3866 > URL: https://issues.jboss.org/browse/ISPN-3866 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.1.Final > Reporter: Guillermo GARCIA OCHOA > Priority: Critical > Fix For: 7.0.0.Final > > > The {{Parser60.parseStore()}} methods ignores all store definition that is not a {{SingleFileStore}} or a {{ClusterLoader}} > {code:java} > private void parseStore(final XMLExtendedStreamReader reader, final ConfigurationBuilderHolder holder) throws XMLStreamException { > ConfigurationBuilder builder = holder.getCurrentConfigurationBuilder(); > CacheLoader store = null; > Boolean fetchPersistentState = null; > Boolean ignoreModifications = null; > Boolean purgeOnStartup = null; > Boolean preload = null; > Boolean shared = null; > // Here it reads the attributes that the AbstractStoreConfiguration defines > for (int i = 0; i < reader.getAttributeCount(); i++) { > ParseUtils.requireNoNamespaceAttribute(reader, i); > String value = replaceProperties(reader.getAttributeValue(i)); > Attribute attribute = Attribute.forName(reader.getAttributeLocalName(i)); > ... > } > // Then it will use the read attributes (and parse the childrens tags) > // if and only if the configure store is a SingleFileStore or ClusterLoader > if (store != null) { > if (store instanceof SingleFileStore) { > ... > parseStoreChildren(reader, sfs); > } else if (store instanceof ClusterLoader) { > ... > parseLoaderChildren(reader, cscb); > } > } > } > {code} > This means that there is no way to set a configuration to my custom cache store with the default parser {{Parser60}}. > If there is another way to what I'm asking for, please let me know because in the documentation only refers to the {{SingleFileStore}} implementation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015