May 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3119) Cleanup the scripts we ship with the distribution

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3119?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3119: -------------------------------- Fix Version/s: (was: 5.3.0.CR1) > Cleanup the scripts we ship with the distribution > -------------------------------------------------- > > Key: ISPN-3119 > URL: https://issues.jboss.org/browse/ISPN-3119 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > Make sure that all the scripts we ship as part of the distribution are correct. Also update the [release process| https://docspace.corp.redhat.com/docs/DOC-28594] with exact stept to test the scripts we ship, e.g. > {quote} > 1. memcached server > $ ./startServer.sh -r memcached > # from a different console test the client > $ ./memcache.py > - ./bin/startServer.sh -r memcached > 2. Pi approximation demo. Open 3 consoles on the same machine > $ ./runPiApproximationDemo.sh > $ ./runPiApproximationDemo.sh > $ ./runPiApproximationDemo.sh -t master > {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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3124) AtomicHashMap.put is not atomic with pessimistic locking

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3124?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3124: -------------------------------- Fix Version/s: (was: 5.3.0.CR1) > AtomicHashMap.put is not atomic with pessimistic locking > -------------------------------------------------------- > > Key: ISPN-3124 > URL: https://issues.jboss.org/browse/ISPN-3124 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.3.0.Final > > > When the user calls {{AtomicHashMap.put(k, v)}}, {{AtomicHashMapProxy.getDeltaMapForWrite()}} first reads the atomic map in the invocation context, and only acquires a lock afterwards. > Between the read and the lock, another transaction can write something to the atomic map, and that write will be lost. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3076: -------------------------------- Fix Version/s: (was: 5.3.0.CR1) > Infinispan should enable use of log4j2 > -------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing > 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). > Also refer: https://issues.jboss.org/browse/ISPN-2976 -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3102) Analyse the performance of MassIndexingTest

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3102?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3102: -------------------------------- Fix Version/s: (was: 5.3.0.CR1) > Analyse the performance of MassIndexingTest > ------------------------------------------- > > Key: ISPN-3102 > URL: https://issues.jboss.org/browse/ISPN-3102 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Blocker > Fix For: 5.3.0.Final > > > MassIndexingTest runs on CI in 10 mins with TRACE on and 3 mins with TRACE off. According to Sanne this shouldn't take that long: > {quote} > sannegrinovero > 11:50 mmarkus: the org.infinispan.query.distributed.MassIndexingTest test is adding 2000 entries to the cache. True that might be a bit excessive, still if it takes 10 minutes you have a problem in Infinispan core. > mmarkus > 11:52 sannegrinovero: each such write is indexed I take it? > sannegrinovero > 11:53 mmarkus: no: withFlags(Flag.SKIP_INDEXING) > 11:54 mmarkus: but it's a 4 node DIST test using Map/Reduce. > sannegrinovero > 11:54 then the Map/Reduce job does some indexing but the indexing engine didn't change overnight > {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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3073) Remove deprecated configuration elements from default JGroups config

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3073?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3073: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.3.0.CR1) > Remove deprecated configuration elements from default JGroups config > -------------------------------------------------------------------- > > Key: ISPN-3073 > URL: https://issues.jboss.org/browse/ISPN-3073 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.3.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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3058) HotRodTargetMigrator swallowing exceptions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3058?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3058: -------------------------------- Fix Version/s: (was: 5.3.0.CR1) > HotRodTargetMigrator swallowing exceptions > ------------------------------------------ > > Key: ISPN-3058 > URL: https://issues.jboss.org/browse/ISPN-3058 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > {code} > try { > cache.get(key); > int i = count.getAndIncrement(); > if (log.isDebugEnabled() && i % 100 == 0) > log.debugf(">> Moved %s keys\n", i); > } catch (Exception e) { > }{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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3062) Add streamLogs=true to JCache testsuite to see TCK output log in console

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3062?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3062: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.3.0.CR1) > Add streamLogs=true to JCache testsuite to see TCK output log in console > ------------------------------------------------------------------------ > > Key: ISPN-3062 > URL: https://issues.jboss.org/browse/ISPN-3062 > Project: Infinispan > Issue Type: Task > Components: JCache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.3.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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3156) Add tests for interoperability mode - reading via REST

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3156?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3156: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.3.0.CR1) > Add tests for interoperability mode - reading via REST > ------------------------------------------------------ > > Key: ISPN-3156 > URL: https://issues.jboss.org/browse/ISPN-3156 > Project: Infinispan > Issue Type: Task > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 5.3.0.Final > > > Add tests for REST: > * accepting application/json and application/xml format of objects stored via HotRod and embedded cache > * read expiry header with HEAD method for objects stored via HotRod and embedded cache -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3146) PrepareCommand triggers RollbackCommand in TxInterceptor if the commit arrives at the same time

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3146?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3146: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.3.0.CR1) > PrepareCommand triggers RollbackCommand in TxInterceptor if the commit arrives at the same time > ----------------------------------------------------------------------------------------------- > > Key: ISPN-3146 > URL: https://issues.jboss.org/browse/ISPN-3146 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Beta2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 5.3.0.Final > > > Total Order only! > When the CommitCommand arrives, it marks the transaction as completed. In TxInterceptor, if the transaction is completed, a RollbackCommand is triggered. Total Order already handles this case and the RollbackCommand will create inconsistencies. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3152) LoadersConfigurationBuilder does not clear existing stores on read()

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3152?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-3152: --------------------------------------- [~maruta.s], what about the following workaround: ConfigurationBuilder builder = new ConfigurationBuilder(); builder.read(manager.getDefaultCacheConfiguration()); builder.loaders().clearCacheLoaders(); builder.eviction().maxEntries(maxEntries)); builder.expiration().lifespan(lifespan); manager.defineConfiguration(name, builder.build()); Cache<String, Object> cache = manager.getCache(name); cache.start(); > LoadersConfigurationBuilder does not clear existing stores on read() > -------------------------------------------------------------------- > > Key: ISPN-3152 > URL: https://issues.jboss.org/browse/ISPN-3152 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.1.Final > Reporter: Marta Sedlakova > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > Hello, > > I am upgrading infinispan configuration and I have following problem: > In old configuration, we use: > Configuration config; > JdbmCacheStoreConfig storeConfig = new JdbmCacheStoreConfig(); > storeConfig.setLocation(location); > storeConfig.setCacheLoaderClassName("org.infinispan.loaders.jdbm.JdbmCacheStore"); > storeConfig.setFetchPersistentState(true); > storeConfig.setIgnoreModifications(false); > storeConfig.setPurgeOnStartup(false); > config = lc.addCacheLoader(storeConfig).build(); > > manager = new DefaultCacheManager(new GlobalConfiguration(), config); > Configuration c = manager.getDefaultConfiguration(); > c.setEvictionMaxEntries(maxEntries); > c.setExpirationLifespan(lifespan); > manager.defineConfiguration(name, c); > And this works fine. Now I am updating to new configuration: > ConfigurationBuilder configuration = new ConfigurationBuilder(); > configuration.invocationBatching().enable(); > JdbmCacheStoreConfigurationBuilder builder = new JdbmCacheStoreConfigurationBuilder(configuration.loaders()); > builder.location(location).fetchPersistentState(true); > configuration.loaders().addStore(builder); > manager = new DefaultCacheManager(new GlobalConfigurationBuilder().build(), configuration.build()); > > And I want to change some properties from previous default configuration for named cache: > > ConfigurationBuilder builder = new ConfigurationBuilder(); > builder.read(manager.getDefaultCacheConfiguration()); > builder.eviction().maxEntries(maxEntries)); > builder.expiration().lifespan(lifespan); > manager.defineConfiguration(name, builder.build()); > Cache<String, Object> cache = manager.getCache(name); > cache.start(); > > But I got following exception: > > org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl.start() on object of type CacheLoaderManagerImpl > at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:883) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:654) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:643) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:546) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:199) > at org.infinispan.CacheImpl.start(CacheImpl.java:559) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545) > at eu.ysoft.cache.ifspn.replicator.IfspnReplicationBuffer.start(IfspnReplicationBuffer.java:117) > at eu.ysoft.cache.replicator.ReplicatorImpl.start(ReplicatorImpl.java:373) > at eu.ysoft.cache.replicator.ReplicatorImpl.start(ReplicatorImpl.java:233) > at eu.ysoft.cache.ifspn.replicator.helpers.IfspnReplicationClient.start(IfspnReplicationClient.java:46) > at eu.ysoft.cache.ifspn.replicator.functional.IfspnTestSimpleReplications.init(IfspnTestSimpleReplications.java:54) > 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:613) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1178) > at org.testng.TestRunner.privateRun(TestRunner.java:757) > at org.testng.TestRunner.run(TestRunner.java:608) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) > at org.testng.TestNG.run(TestNG.java:999) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) > at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:203) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174) > at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:111) > Caused by: org.infinispan.CacheException: Unable to start cache loaders > at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:160) > 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.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203) > ... 42 more > Caused by: java.lang.Exception: Invalid cache loader configuration!! Only ONE cache loader may have fetchPersistentState set to true. Cache will not start! > at org.infinispan.loaders.CacheLoaderManagerImpl.createCacheLoader(CacheLoaderManagerImpl.java:324) > at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:146) > ... 47 more > > > I need some help how to solve this issue, when we were using the old deprecated configuration, this configuration scenarion works. > Thanks > Marta -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013