January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1788) infinispan-5.1.xsd out of sync with StAX parser

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-1788: ---------------------------------- Summary: infinispan-5.1.xsd out of sync with StAX parser Key: ISPN-1788 URL: https://issues.jboss.org/browse/ISPN-1788 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.FINAL Reporter: Paul Ferraro Assignee: Manik Surtani There are some inconsistencies between the infinispan-5.1.xsd schema in the 5.1.0.FINAL jar and the StAX parser. Here are a few inconsistencies I've noticed so far: 1. parser recognizes <stateTransfer/> element, which does not exist in the xsd 2. parser recognizes <storeAsBinary enabled="true|false"/> attribute, which does not exist in xsd I recommend you create a unit tests that validates a fully specified xml file against the schema. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] (ISPN-1813) Javadoc wrong on ClusteringConfigurationBuilder.stateTransfer()

by Pete Muir (JIRA)

Pete Muir created ISPN-1813: ------------------------------- Summary: Javadoc wrong on ClusteringConfigurationBuilder.stateTransfer() Key: ISPN-1813 URL: https://issues.jboss.org/browse/ISPN-1813 Project: Infinispan Issue Type: Bug Components: Configuration Reporter: Pete Muir Assignee: Dan Berindei Priority: Minor It says /** * Configure sync sub element. Once this method is invoked users cannot subsequently invoke * <code>configureAsync()</code> as two are mutually exclusive */ @Override public StateTransferConfigurationBuilder stateTransfer() { return stateTransferConfigurationBuilder; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1805) Remove or downgrade "Passivation configured without a valid eviction policy" startup warning.

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-1805: ---------------------------------- Summary: Remove or downgrade "Passivation configured without a valid eviction policy" startup warning. Key: ISPN-1805 URL: https://issues.jboss.org/browse/ISPN-1805 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.1.0.FINAL Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Minor Wanting full manual control over passivation (by calling evict()) is a perfectly valid use case and is the default configuration for web and sfsb replication in the AS. Can we remove this startup WARNing? or at least downgrade it to INFO? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1777) Add LoadersConfigurationBuilder.clearCacheLoaders() method

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-1777: ---------------------------------- Summary: Add LoadersConfigurationBuilder.clearCacheLoaders() method Key: ISPN-1777 URL: https://issues.jboss.org/browse/ISPN-1777 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 5.1.0.CR4 Reporter: Paul Ferraro Assignee: Manik Surtani The use case for this is defining a cache for web session replication for a single application. The cache needs a unique file cache store location. The only way to modify the location is by copy each sub-builder except the loaders builder, and copying the loader properties manually. The ability to clear cache loaders of a builder would simplify this greatly. e.g. I could replace: ConfigurationBuilder builder = new ConfigurationBuilder().name(config.name()); // Copy everything except loaders builder.clustering().read(config.clustering()) .customInterceptors().read(config.customInterceptors()) .dataContainer().read(config.dataContainer()) .deadlockDetection().read(config.deadlockDetection()) .eviction().read(config.eviction()) .expiration().read(config.expiration()) .indexing().read(config.indexing()) .invocationBatching().read(config.invocationBatching()) .jmxStatistics().read(config.jmxStatistics()) .locking().read(config.locking()) .storeAsBinary().enable().storeKeysAsBinary(false).storeValuesAsBinary(true) .transaction().read(config.transaction()) .versioning().read(config.versioning()) ; if (!config.loaders().cacheLoaders().isEmpty()) { builder.loaders().clearCacheLoaders(); // Our cache needs a unique passivation location for (AbstractLoaderConfiguration loader: config.loaders().cacheLoaders()) { this.addCacheLoader(builder.loaders(), loader, manager) .async().read(loader.async()) .singletonStore().read(loader.singletonStore()) ; } } with: ConfigurationBuilder builder = new ConfigurationBuilder().read(config); builder.loaders().clearCacheLoaders(); // Our cache needs a unique passivation location for (AbstractLoaderConfiguration loader: config.loaders().cacheLoaders()) { this.addCacheLoader(builder.loaders(), loader, manager) .async().read(loader.async()) .singletonStore().read(loader.singletonStore()) ; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] (ISPN-1810) Default to larger timeouts for keep-alive of JGroup threads

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1810: ------------------------------------- Summary: Default to larger timeouts for keep-alive of JGroup threads Key: ISPN-1810 URL: https://issues.jboss.org/browse/ISPN-1810 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.1.1.CR1, 5.1.1.FINAL, 5.2.0.ALPHA1 After some performance tests it seems better to have a stable amount of threads in the ThreadPool rather than stopping and restarting threads too often. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] (ISPN-1807) Write skew checks fail when using replicated mode

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1807: ----------------------------------- Summary: Write skew checks fail when using replicated mode Key: ISPN-1807 URL: https://issues.jboss.org/browse/ISPN-1807 Project: Infinispan Issue Type: Bug Components: Distributed Cache, Transactions Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Mircea Markus Priority: Blocker Fix For: 5.1.1.CR1, 5.1.1.FINAL Write skews are not correctly detected when in replicated mode. This works fine in distributed mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1789) LoaderConfigurationBuilder validation is wrong

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-1789: ---------------------------------- Summary: LoaderConfigurationBuilder validation is wrong Key: ISPN-1789 URL: https://issues.jboss.org/browse/ISPN-1789 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.FINAL Reporter: Paul Ferraro Assignee: Manik Surtani LoaderConfigurationBuilder.validate() tests for the following condition: if (!getLoadersBuilder().shared() && fetchPersistentState && purgeOnStartup && getBuilder().clustering().cacheMode().isClustered()) { log.staleEntriesWithoutFetchPersistentStateOrPurgeOnStartup(); } The error message reads: "Fetch persistent state and purge on startup are both disabled, cache may contain stale entries on startup" However, the condition tests for the case where fetch persistent state and purge are both *enabled*. The result is a misleading WARN message in the logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] (ISPN-1786) very bad distribution of keys (DIST mode) in 5.1

by Mircea Markus (JIRA)

Mircea Markus created ISPN-1786: ----------------------------------- Summary: very bad distribution of keys (DIST mode) in 5.1 Key: ISPN-1786 URL: https://issues.jboss.org/browse/ISPN-1786 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Mircea Markus Assignee: Mircea Markus Priority: Critical Fix For: 5.2.0.FINAL Here's the result form an radargun benchmark. Key distribution in 5.0.Final: Cluster size: 4 -> ( 9818 10242 9898 9899) Cluster size: 6 -> ( 9724 9585 10152 9964 9739 10115) Cluster size: 8 -> ( 9260 9680 9971 9378 10079 10086 10274 10017) Key distribution in 5.1.Final: Cluster size: 4 -> ( 15505 13698 5918 4482) Cluster size: 6 -> ( 8761 7820 17145 8188 12827 4183) Cluster size: 8 -> ( 8391 6302 10773 22068 3589 200 3050 25211) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
8
0 / 0

[JBoss JIRA] (ISPN-1798) forceReturnValues parameter to RemoteCacheManager.createCache() is ignored!

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1798: ----------------------------------- Summary: forceReturnValues parameter to RemoteCacheManager.createCache() is ignored! Key: ISPN-1798 URL: https://issues.jboss.org/browse/ISPN-1798 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL As per subject -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] (ISPN-1779) IllegalArgumentException on TimSort

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1779: -------------------------------------- Summary: IllegalArgumentException on TimSort Key: ISPN-1779 URL: https://issues.jboss.org/browse/ISPN-1779 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Affects Versions: 5.1.0.CR4 Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.1.0.FINAL {code}16:15:51,484 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (http-localhost.localdomain-127.0.0.1-8080-9) ISPN000136: Execution error: java.lang.IllegalArgumentException: Comparison method violates its general contract! at org.infinispan.util.TimSort.mergeLo(TimSort.java:751) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.util.TimSort.mergeAt(TimSort.java:487) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.util.TimSort.mergeCollapse(TimSort.java:412) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.util.TimSort.sort(TimSort.java:218) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.util.TimSort.sort(TimSort.java:177) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.sort(OptimisticLockingInterceptor.java:252) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitPrepareCommand(OptimisticLockingInterceptor.java:94) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.NotificationInterceptor.visitPrepareCommand(NotificationInterceptor.java:58) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.TxInterceptor.visitPrepareCommand(TxInterceptor.java:106) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.StateTransferLockInterceptor.handleWithRetries(StateTransferLockInterceptor.java:201) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.StateTransferLockInterceptor.visitPrepareCommand(StateTransferLockInterceptor.java:81) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:76) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:116) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.BatchingInterceptor.handleDefault(BatchingInterceptor.java:86) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:113) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.commands.tx.PrepareCommand.acceptVisitor(PrepareCommand.java:131) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:345) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.transaction.TransactionCoordinator.commit(TransactionCoordinator.java:159) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at org.infinispan.transaction.xa.TransactionXaAdapter.commit(TransactionXaAdapter.java:125) [infinispan-core-5.1.0.CR4.jar:5.1.0.CR4] at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelCommit(XAResourceRecord.java:451) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012