October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2930) ChainingCacheLoaderTest intermittent failure

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2930?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2930: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > ChainingCacheLoaderTest intermittent failure > -------------------------------------------- > > Key: ISPN-2930 > URL: https://issues.jboss.org/browse/ISPN-2930 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Test Suite > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Pedro Ruivo > Labels: testsuite_stability > Attachments: ChainingCacheLoaderTest.log > > > Test fails sometimes. See attached log. -- 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-2929) Fix quickstart license and white space issues exposed by qstool report

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2929?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2929: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Fix quickstart license and white space issues exposed by qstool report > ---------------------------------------------------------------------- > > Key: ISPN-2929 > URL: https://issues.jboss.org/browse/ISPN-2929 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Pedro Ruivo > Priority: Minor > > As a result of the face-to-face discussion on how to keep the quickstarts consistent and make maintenance less error-prone, Rafael has created a tool to automate this process. > Rafael updated all files with the correct license information as part of this commit: https://github.com/jboss-jdf/jboss-as-quickstart/commit/c6dc9668e7ce63861... > I have submitted a pull to correct most of the whitespace and tab issues: > https://github.com/jboss-jdf/jboss-as-quickstart/pull/474 > You need to fix these issues upstream. > You can find information about how to use Rafael's tool on the bottom of the page under "How to use Rafael's Tool" here: > https://docspace.corp.redhat.com/docs/DOC-132902 -- 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-2901) Update the configuration files for xsite documentation

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2901?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2901: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Update the configuration files for xsite documentation > ------------------------------------------------------ > > Key: ISPN-2901 > URL: https://issues.jboss.org/browse/ISPN-2901 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > > The xsite configuration files are not correct and require updating: https://docs.jboss.org/author/pages/viewpageattachments.action?pageId=544... -- 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-2898) Web Cache fails to start when multiple apps are trying to create it

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2898?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2898: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Web Cache fails to start when multiple apps are trying to create it > ------------------------------------------------------------------- > > Key: ISPN-2898 > URL: https://issues.jboss.org/browse/ISPN-2898 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.1.7.Final > Reporter: Shay Matasaro > Assignee: Dan Berindei > > When multiple apps are trying to create/connect to the web cache , the fist one get a lock on the cache manager, and prevents the others from starting it in a timely manner -- 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-2838) Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2838?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2838: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Remote configuration in the arquillian.xml file should be commented - See JDF-215 for details > --------------------------------------------------------------------------------------------- > > Key: ISPN-2838 > URL: https://issues.jboss.org/browse/ISPN-2838 > Project: Infinispan > Issue Type: Enhancement > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Pedro Ruivo > > The kitchensink-deltaspike arquillian.xml file contains a configuration for jbossHome > This should be commented out. All the remote configuration in the arquillian files should look like the following: >  > <container qualifier="jboss" default="true"> >  >  >  >  > </container> > You can copy and paste from the bean-validation arquillian.xml file. -- 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-2895) org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2895?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2895: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly > -------------------------------------------------------------------------------- > > Key: ISPN-2895 > URL: https://issues.jboss.org/browse/ISPN-2895 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.2.Final > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Labels: stable_embedded_query, testsuite_stability > > The test fails randomly and the error message is: > {code} > java.lang.NullPointerException > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:76) > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:56) > at org.infinispan.lucene.InfinispanDirectoryIOTest.verifyOnBuffer(InfinispanDirectoryIOTest.java:184) > at org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile(InfinispanDirectoryIOTest.java:153) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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:722) > {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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2811) cassandraStore xml configuration gives parser error on attributes "username" and "password"

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2811?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2811: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > cassandraStore xml configuration gives parser error on attributes "username" and "password" > ------------------------------------------------------------------------------------------- > > Key: ISPN-2811 > URL: https://issues.jboss.org/browse/ISPN-2811 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.0.Final > Reporter: Giovanni Mels > Assignee: Tristan Tarrant > > This is because attributes "username" and "password" are in uppercase in [org.infinispan.loaders.cassandra.configuration.Attribute|https://github.c...], but in lowercase in the [schema|http://docs.jboss.org/infinispan/schemas/infinispan-cachestore-cas...]. > {quote} > org.infinispan.config.ConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[37,142] > Message: Unexpected attribute 'password' encountered > at org.infinispan.configuration.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:76) > at org.infinispan.configuration.parsing.Parser52.parseCommonStoreAttributes(Parser52.java:696) > at org.infinispan.loaders.cassandra.configuration.CassandraCacheStoreConfigurationParser52.parseCassandraStoreAttributes(CassandraCacheStoreConfigurationParser52.java:180) > at org.infinispan.loaders.cassandra.configuration.CassandraCacheStoreConfigurationParser52.parseCassandraStore(CassandraCacheStoreConfigurationParser52.java:77) > at org.infinispan.loaders.cassandra.configuration.CassandraCacheStoreConfigurationParser52.readElement(CassandraCacheStoreConfigurationParser52.java:65) > at org.infinispan.loaders.cassandra.configuration.CassandraCacheStoreConfigurationParser52.readElement(CassandraCacheStoreConfigurationParser52.java:43) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) > at org.infinispan.configuration.parsing.Parser52.parseLoaders(Parser52.java:588) > at org.infinispan.configuration.parsing.Parser52.parseCache(Parser52.java:180) > at org.infinispan.configuration.parsing.Parser52.parseDefaultCache(Parser52.java:145) > at org.infinispan.configuration.parsing.Parser52.readElement(Parser52.java:98) > 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) > ... 28 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-2810) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2810?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2810: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be 0 > -------------------------------------------------------------------------------- > > Key: ISPN-2810 > URL: https://issues.jboss.org/browse/ISPN-2810 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 5.2.0.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > > Contrary to what ISPN-732 says, timeToLiveSeconds=0 and maxIdleTimeSeconds=0 are now treated correctly by the server and the entry is stored in the cache with the default lifespan/maxIdle. > But if the user PUTs or POSTs an entry and doesn't specify timeToLiveSeconds=0 and maxIdleTimeSeconds=0 explicitly, the entries are stored with infinite lifespan/maxIdle. -- 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-2799) Deprecated OverrideDefault annotation is the only way to prevent construction of the default CacheManager

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2799?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2799: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Deprecated OverrideDefault annotation is the only way to prevent construction of the default CacheManager > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-2799 > URL: https://issues.jboss.org/browse/ISPN-2799 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Affects Versions: 5.2.0.Final > Reporter: Emond Papegaaij > Assignee: Pete Muir > > The signature of DefaultEmbeddedCacheManagerProducer.getDefaultEmbeddedCacheManager, with @OverrideDefault, causes the providedDefaultEmbeddedCacheManager to only be satisfied when your producer method is annotated with @OverrideDefault. > For example: > {code} > @Produces > @ApplicationScoped > @Default > @OverrideDefault > public EmbeddedCacheManager defaultEmbeddedCacheManager() { > return new DefaultCacheManager( > new GlobalConfigurationBuilder() > .globalJmxStatistics().allowDuplicateDomains(true) > .cacheManagerName("CDICacheManager").enable().build(), > new ConfigurationBuilder().jmxStatistics().disable() > .eviction().strategy(EvictionStrategy.LRU) > .maxEntries(10000).build()); > } > {code} > If I remove @OverrideDefault, my CacheManager is still used as the default CacheManager, but the CacheManager from DefaultEmbeddedCacheManagerProducer is also instantiated. This happens because DefaultCacheResolver iterates over all EmbeddedCacheManagers to check if one of them contains a specific cache. > The default CacheManager is giving me problems because it conflicts with another CacheManager (probably from JBoss AS) in JMX. -- 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-2990) L1ManagerImpl doesn't reliably invalidate with async caches

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2990?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2990: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > L1ManagerImpl doesn't reliably invalidate with async caches > ----------------------------------------------------------- > > Key: ISPN-2990 > URL: https://issues.jboss.org/browse/ISPN-2990 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.1.Final > Reporter: Sebastian Tusk > Assignee: William Burns > Priority: Minor > Labels: onboard > > B is owner of k,v1 > A has k,v1 in L1 > 1. TX: A puts k,v2 > 2. TX: A sends async PrepareCommand k,v2 to B (one-phase-commit) > 3. TX: A removes k,v1 from L1 > 4. A putForExternalRead k,v1 and has it in L1 again > 5. TX: B executes PrepareCommand k,v2 but doesn't send invalidation to origin > Result: A has k,v1 and B has k,v2 > Solution: For async caches send invalidation to origin too. > The problem is that the owner updates the cache entry asynchronously. This gives the origin of the transaction time to request the entry. Here an outdated version is received and placed in L1. The owner never invalidates the entry and as result the cache is inconsistent. -- 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