October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3621) Most CacheStore configuration examples in the documentation are wrong (outdated)

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3621?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-3621: ---------------------------------- Affects Version/s: 6.0.0.CR1 > Most CacheStore configuration examples in the documentation are wrong (outdated) > -------------------------------------------------------------------------------- > > Key: ISPN-3621 > URL: https://issues.jboss.org/browse/ISPN-3621 > Project: Infinispan > Issue Type: Bug > Components: Documentation > Affects Versions: 6.0.0.CR1 > Reporter: Sanne Grinovero > Assignee: Mircea Markus > Fix For: 6.0.0.CR2, 6.0.0.Final > > > I've been trying half a dozen configuration snippets from the documentation, I couldn't get any CacheStore to work. All I get from the configuration parser is an unhelpfull stack trace: > {quote} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[50,63] > Message: Unexpected element '{urn:infinispan:config:6.0}loaders' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedElement(ParseUtils.java:35) > at org.infinispan.configuration.parsing.Parser60.parseCache(Parser60.java:178) > at org.infinispan.configuration.parsing.Parser60.parseNamedCache(Parser60.java:109) > at org.infinispan.configuration.parsing.Parser60.readElement(Parser60.java:76) > at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:130) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:112) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:99) > at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:86) > ... 47 more > {quote} > One might think that something (what?) is wrong at [row,col]:[50,63] but I'm copy pasting the documentation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2478) PutMapCommand not correctly removing previous types from indexes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2478?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2478: -------------------------------- Fix Version/s: 6.0.0.CR2 > PutMapCommand not correctly removing previous types from indexes > ---------------------------------------------------------------- > > Key: ISPN-2478 > URL: https://issues.jboss.org/browse/ISPN-2478 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.1.8.Final > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: stable_embedded_query > Fix For: 6.0.0.CR2, 6.0.0.Final > > > We need to perform certain cleanup operations - potentially - on the return types of commands such as put and remove. In case of a putAll command, we're ignoring this requirement. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2478) PutMapCommand not correctly removing previous types from indexes

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-2478?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-2478: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > PutMapCommand not correctly removing previous types from indexes > ---------------------------------------------------------------- > > Key: ISPN-2478 > URL: https://issues.jboss.org/browse/ISPN-2478 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.1.8.Final > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: stable_embedded_query > Fix For: 6.0.0.Final > > > We need to perform certain cleanup operations - potentially - on the return types of commands such as put and remove. In case of a putAll command, we're ignoring this requirement. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3611) Service jboss.infinispan.default failed to start on IBM JDK 6, argument type mismatch

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3611?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3611: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Service jboss.infinispan.default failed to start on IBM JDK 6, argument type mismatch > ------------------------------------------------------------------------------------- > > Key: ISPN-3611 > URL: https://issues.jboss.org/browse/ISPN-3611 > Project: Infinispan > Issue Type: Bug > Reporter: Mircea Markus > Assignee: William Burns > Labels: jdg62GAblocker > Fix For: 6.0.0.CR2 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3619) Upgrade logging processor to 1.1.0.Final

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3619?page=com.atlassian.jira.plugin.... ] Pedro Ruivo resolved ISPN-3619. ------------------------------- Resolution: Done > Upgrade logging processor to 1.1.0.Final > ---------------------------------------- > > Key: ISPN-3619 > URL: https://issues.jboss.org/browse/ISPN-3619 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Sanne Grinovero > Fix For: 6.0.0.CR2, 6.0.0.Final > > > <sanne> > I've tried to upgrade the version to 1.1.0.Final (from 1.0.3.Final) and it seems flawless. take it > </sanne> -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3596) LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3596?page=com.atlassian.jira.plugin.... ] Adrian Nistor resolved ISPN-3596. --------------------------------- Resolution: Duplicate Issue Duplicates ISPN-3620. > LifecycleManager of query module should use the Provider mechanism instead of relying on brute class loading > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-3596 > URL: https://issues.jboss.org/browse/ISPN-3596 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 6.0.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > This is used to customize the SearchFactory programmatic mappings only if remote query module is present 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3617) Inconsistent L1 in non-tx distributed cache

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3617?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3617: ------------------------------------- Side note if we introduced a fix with ISPN-3426 that makes it so we only put L1 entries when retrieved from the owner this wouldn't be an issue. > Inconsistent L1 in non-tx distributed cache > ------------------------------------------- > > Key: ISPN-3617 > URL: https://issues.jboss.org/browse/ISPN-3617 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.7.Final > Reporter: Radim Vansa > Assignee: William Burns > Labels: jdg62blocker > Fix For: 6.0.0.CR2, 6.0.0.Final > > > When the change is replicated to backup owner, it sends the InvalidateL1Command to backup owners before committing the entry in EntryWrappingInterceptor (it performs the WriteCommand in parallel with sending the invalidation commmand, but then it waits until the invalidation request gets acked. If a GET is executed between the invalidation and committing the entry, the response contains outdated result and the L1 will not be invalidated until next write operation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3620) Move the programmatic search mappings required by remote query out of query module ModuleLifecycle

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3620?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3620: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2162 > Move the programmatic search mappings required by remote query out of query module ModuleLifecycle > -------------------------------------------------------------------------------------------------- > > Key: ISPN-3620 > URL: https://issues.jboss.org/browse/ISPN-3620 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 6.0.0.CR1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 6.0.0.CR2 > > > Currently this was worked around by reflection hacks but the proper way to solve this is to use the Provider mechanism. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3620) Move the programmatic search mappings required by remote query out of query module ModuleLifecycle

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-3620: ----------------------------------- Summary: Move the programmatic search mappings required by remote query out of query module ModuleLifecycle Key: ISPN-3620 URL: https://issues.jboss.org/browse/ISPN-3620 Project: Infinispan Issue Type: Enhancement Components: Querying Affects Versions: 6.0.0.CR1 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 6.0.0.CR2 Currently this was worked around by reflection hacks but the proper way to solve this is to use the Provider mechanism. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3364) Tests from org.infinispan.atomic package fail with AssertionError

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3364?page=com.atlassian.jira.plugin.... ] Work on ISPN-3364 stopped by William Burns. > Tests from org.infinispan.atomic package fail with AssertionError > ----------------------------------------------------------------- > > Key: ISPN-3364 > URL: https://issues.jboss.org/browse/ISPN-3364 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 6.0.0.Alpha1 > Environment: RHEL5_x86, RHEL5_x86_64, RHEL6_x86, RHEL5_x86_64 with IBM JDK7 > Reporter: Vitalii Chepeliuk > Assignee: William Burns > Labels: jdg62GAblocker, testsuite_stability > Attachments: LocalDeltaAwarePassivationTest.log.zip, ReplDeltaAwarePassivationTest.log.zip > > > Following tests fail from org.infinispan.atomic package > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap2 > Add link on jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2013