February 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-335) fetchPersistentState generate an exception

by Huu-Dong Quach (JIRA)

fetchPersistentState generate an exception ------------------------------------------ Key: ISPN-335 URL: https://jira.jboss.org/jira/browse/ISPN-335 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.0.0.CR3 Environment: Windows 7, Mac OS X, Ubuntu, RHEL 4 Reporter: Huu-Dong Quach Assignee: Manik Surtani In a clustered replicated cache, when I flag the fetchPersistentState attribute to true for a FileStore, Infinispan generate an exception. Also, if I set the preload attribute to true, I expect the store to fetch the persistant state before loading the data from the store but that's not the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-331) Fix core jar/lib locations in scripts

by Galder Zamarreno (JIRA)

Fix core jar/lib locations in scripts ------------------------------------- Key: ISPN-331 URL: https://jira.jboss.org/jira/browse/ISPN-331 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.GA Location of core jars have changed, modify and test scripts accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-276) Expensive to read a single byte in Lucene Directory

by Sanne Grinovero (JIRA)

Expensive to read a single byte in Lucene Directory --------------------------------------------------- Key: ISPN-276 URL: https://jira.jboss.org/jira/browse/ISPN-276 Project: Infinispan Issue Type: Bug Components: Lucene Directory Affects Versions: 4.0.0.CR2, 4.0.0.CR1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.GA public byte readByte() in org.infinispan.lucene.InfinispanIndexIO is doing some expensive operations, while this is a very hot spot. Spotted by Earwin Burrfoot on Lucene's developer list. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-281) REST server should be configurable

by Manik Surtani (JIRA)

REST server should be configurable ---------------------------------- Key: ISPN-281 URL: https://jira.jboss.org/jira/browse/ISPN-281 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.0.0.CR2 Reporter: Manik Surtani Assignee: Michael Neale Fix For: 4.0.0.GA Currently the WAR file we build and distribute uses a static cache configuration, embedded in the WAR file. We need to think of a way to have this configurable. One idea would be to ship with, say, 5 different config files in the WAR: * cache-local.xml * cache-dist-sync.xml * cache-dist-async.xml * cache-repl-sync.xml * cache-repl-async.xml ... and the servlet starts the appropriate config based on JVM params (eg., -Dinfinispan.server.rest.cfg=cache-local.xml) Also, cache-local.xml should be the default since running the WAR file with incorrect or inappropriate cluster settings prevents startup. Finally perhaps there should be a way to customise the cfg even further - perhaps the default web page could offer a way to upload a config file and restart the cache using this instead? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-321) NPE if custom interceptor is created from xml configuration

by Alexander Kosenkov (JIRA)

NPE if custom interceptor is created from xml configuration ----------------------------------------------------------- Key: ISPN-321 URL: https://jira.jboss.org/jira/browse/ISPN-321 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.0.0.CR3 Reporter: Alexander Kosenkov Assignee: Manik Surtani Add to config something like this: <customInterceptors> <interceptor after="org.infinispan.interceptors.CacheLoaderInterceptor" class="com.devexperts.PersistenceInterceptor"/> </customInterceptors> and it will fail Caused by: java.lang.NullPointerException at org.infinispan.interceptors.InterceptorChain.addInterceptorAfter(InterceptorChain.java:193) at org.infinispan.factories.InterceptorChainFactory.buildCustomInterceptors(InterceptorChainFactory.java:161) at org.infinispan.factories.InterceptorChainFactory.buildInterceptorChain(InterceptorChainFactory.java:143) at org.infinispan.factories.InterceptorChainFactory.construct(InterceptorChainFactory.java:177) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-285) Enhance test fwk to avoid JMX domains collisions

by Mircea Markus (JIRA)

Enhance test fwk to avoid JMX domains collisions ------------------------------------------------- Key: ISPN-285 URL: https://jira.jboss.org/jira/browse/ISPN-285 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA A possible solution would be: - jmx disabled by default (The TestCacheManagerFactory might do this) - new TestCacheManagerFactory method would receive the jmx domain. It will keep track of all active domains and won't allow two CacheManagers with same domain name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-245) Core module to delegate lifecycle events to sub-modules

by Manik Surtani (JIRA)

Core module to delegate lifecycle events to sub-modules ------------------------------------------------------- Key: ISPN-245 URL: https://jira.jboss.org/jira/browse/ISPN-245 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Follow a 'service registry' style approach to delegating lifecycle events so that modules can register for hooks. The purpose behind this is that some modules need to perform some setup. E.g., the 'tree' module needs to register specific types with the Marshaller. The 'query' module needs to register an interceptor with the Cache if the Cache has enabled querying. Etc. The approach is to use a JDK service registry style approach. The Core module defines a ModuleLifecycle interface: interface ModuleLifecycle { void cacheManagerStarting(GlobalComponentRegistry gcr); void cacheManagerStarted(GlobalComponentRegistry gcr); void cacheManagerStopping(GlobalComponentRegistry gcr); void cacheManagerStopped(GlobalComponentRegistry gcr); void cacheStarting(ComponentRegistry cr, String cacheName); void cacheStarted(ComponentRegistry cr, String cacheName); void cacheStopping(ComponentRegistry cr, String cacheName); void cacheStopped(ComponentRegistry cr, String cacheName); } each module would implement this interface. "Registration" is performed by each module maintaining a infinispan-module-info.properties file in its classpath, containing: infinispan.module.lifecycle=<ModuleLifecycle impl> The DefaultCacheManager, when starting up, scans its classpath for "infinispan-module-info.properties" and registers all listeners. Everytime the cache manager starts, stops, or caches start or stop, the appropriate callbacks are invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-339) Lucene demo not working in standalone transactions

by Sanne Grinovero (JIRA)

Lucene demo not working in standalone transactions -------------------------------------------------- Key: ISPN-339 URL: https://jira.jboss.org/jira/browse/ISPN-339 Project: Infinispan Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.GA since jbossjts was upgraded from 4.6.0.GA to 4.9.0.GA the Lucene directory demo throws exceptions about a missing ORB : FATAL com.arjuna.ats.jts.logging.loggerI18N - [com.arjuna.ats.internal.jts.ORBManager] The ORB has not been initialized yet Exception in thread "main" com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:94) at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:332) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1239) at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:74) at org.infinispan.context.InvocationContextContainerImpl.getRunningTx(InvocationContextContainerImpl.java:147) at org.infinispan.context.InvocationContextContainerImpl.createInvocationContext(InvocationContextContainerImpl.java:57) at org.infinispan.CacheDelegate.getInvocationContext(CacheDelegate.java:287) at org.infinispan.CacheDelegate.get(CacheDelegate.java:199) at org.infinispan.lucene.InfinispanDirectory.getFileList(InfinispanDirectory.java:220) at org.infinispan.lucene.InfinispanDirectory.list(InfinispanDirectory.java:96) at org.infinispan.lucene.InfinispanDirectory.listAll(InfinispanDirectory.java:263) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-324) Cache.clear() raises a NPE if CahceMode is DIST_SYNC and NumOwners is set to 1

by Marco Ferrante (JIRA)

Cache.clear() raises a NPE if CahceMode is DIST_SYNC and NumOwners is set to 1 ------------------------------------------------------------------------------ Key: ISPN-324 URL: https://jira.jboss.org/jira/browse/ISPN-324 Project: Infinispan Issue Type: Bug Affects Versions: 4.0.0.CR3 Reporter: Marco Ferrante Assignee: Manik Surtani Priority: Minor This fragment: GlobalConfiguration gc = GlobalConfiguration.getClusteredDefault(); Configuration config = new Configuration(); config.setCacheMode(Configuration.CacheMode.DIST_SYNC); config.setNumOwners(1); // no redundancy CacheManager cacheManager = new DefaultCacheManager(gc, config); Cache cache = cacheManager.getCache(); cache.put("key", "value"); cache.clear(); assert cache.isEmpty(); raises a NullPointerException at cache.clear() invokation. It works correctly both using other cache modes (LOCAL, REPL and INVALIDATION) or avoiding to set config.setNumOwners to 1. The stacktrace is: java.lang.NullPointerException at org.infinispan.interceptors.DistributionInterceptor.isSingleOwnerAndLocal(DistributionInterceptor.java:317) at org.infinispan.interceptors.DistributionInterceptor.handleWriteCommand(DistributionInterceptor.java:276) at org.infinispan.interceptors.DistributionInterceptor.visitClearCommand(DistributionInterceptor.java:180) at org.infinispan.commands.write.ClearCommand.acceptVisitor(ClearCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.LockingInterceptor.visitClearCommand(LockingInterceptor.java:169) at org.infinispan.commands.write.ClearCommand.acceptVisitor(ClearCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132) .... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-327) Allow AsyncStore to retry and be extensible

by Bryan Grunow (JIRA)

Allow AsyncStore to retry and be extensible ------------------------------------------- Key: ISPN-327 URL: https://jira.jboss.org/jira/browse/ISPN-327 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 4.0.0.CR3 Reporter: Bryan Grunow Assignee: Manik Surtani In the current implementation of AsyncStore if the data cannot be stored to the backend then the change is lost. It would be nice for AsyncStore to queue up changes and retry. Along with providing retries it would be nice to make the AsyncStore class more extensible such that custom logic can be implemented to facilitate the retries and excpetion behaviors. This issues was originally raised in the user discussion http://community.jboss.org/thread/146008?tstart=0 by Alexander Kosenkov. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2010