September 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-578) BDB store logs license information relating to JBoss Cache instead of Infinispan

by Sanne Grinovero (JIRA)

BDB store logs license information relating to JBoss Cache instead of Infinispan -------------------------------------------------------------------------------- Key: ISPN-578 URL: https://jira.jboss.org/browse/ISPN-578 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.CR2, 4.0.0.Final Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 4.1.0.CR3, 5.0.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-316) Add aliasing capability to DefaultCacheManager

by Brian Stansberry (JIRA)

Add aliasing capability to DefaultCacheManager ---------------------------------------------- Key: ISPN-316 URL: https://jira.jboss.org/jira/browse/ISPN-316 Project: Infinispan Issue Type: Feature Request Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 4.1.0.CR1 The JBoss AS impl of the JBC CacheManager supports aliasing of cache configuration names. DefaultCacheManager can do the same. Helpful for preserving configuration compatibility across releases, e.g. an EJB3 bean class annotated with @CacheConfig(name="jboss.cache:service=EJB3SFSBClusteredCache") to work in AS 4.2 still works in AS 5 because I made "jboss.cache:service=EJB3SFSBClusteredCache" an alias for "sfsb-cache". This doesn't affect the CacheManager API; it's an implementation detail; just inject a map of aliases and then resolve any unknown configuration names against it. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-510) Simplify InfinispanIndexIO

by Sanne Grinovero (JIRA)

Simplify InfinispanIndexIO -------------------------- Key: ISPN-510 URL: https://jira.jboss.org/browse/ISPN-510 Project: Infinispan Issue Type: Task Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 4.1.0.CR1, 5.0.0.BETA1 org.infinispan.lucene.InfinispanIndexIO is unnededly long and is containing a class to manage input and one for output, as two independent inner classes. Refactor the two componentes as top level classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-617) Log performed DDL statements in JDBC Cachestores

by Sanne Grinovero (JIRA)

Log performed DDL statements in JDBC Cachestores ------------------------------------------------ Key: ISPN-617 URL: https://jira.jboss.org/browse/ISPN-617 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.1.0.CR3 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 4.1.0.Final, 5.0.0.BETA1 The executeUpdateSql method in org.infinispan.loaders.jdbc.TableManipulation is currently not logging statements -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-673) Stopped cache still causing RPC timeouts on caller.

by Paul Ferraro (JIRA)

Stopped cache still causing RPC timeouts on caller. --------------------------------------------------- Key: ISPN-673 URL: https://jira.jboss.org/browse/ISPN-673 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 4.2.0.ALPHA2 Reporter: Paul Ferraro Assignee: Manik Surtani Revision 2384 of org.infinispan.remoting.InboundInvocationHandlerImpl adds an 30 second wait loop for stopped caches, causing RPCs to timeout. For a stopped cache, GlobalComponentRegistry.getNamedComponentRegistry(...) returns null, since its global component registry entry is removed during ComponentRegistry.stop(), yet isDefined(...) will still return true. When not using strict peer to peer, this delay is inappropriate and causes the RPC to timeout. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
7
0 / 0

[JBoss JIRA] Created: (ISPN-497) Upgrade Lucene to 2.9.3

by Sanne Grinovero (JIRA)

Upgrade Lucene to 2.9.3 ----------------------- Key: ISPN-497 URL: https://jira.jboss.org/browse/ISPN-497 Project: Infinispan Issue Type: Task Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 4.1.0.CR1, 5.0.0.BETA1 Several bugfixes made it into Lucene 2.9.3, some of which where preventing us to commit some tests as they where failing because of Lucene's erratic behaviour during commits at high load. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-527) Implement Read-Locks for Lucene rename

by Sanne Grinovero (JIRA)

Implement Read-Locks for Lucene rename -------------------------------------- Key: ISPN-527 URL: https://jira.jboss.org/browse/ISPN-527 Project: Infinispan Issue Type: Sub-task Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.1.0.CR1, 5.0.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-526) Implement Read-Locks for Lucene delete

by Sanne Grinovero (JIRA)

Implement Read-Locks for Lucene delete -------------------------------------- Key: ISPN-526 URL: https://jira.jboss.org/browse/ISPN-526 Project: Infinispan Issue Type: Sub-task Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.1.0.CR1, 5.0.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-646) Move Query Module to use Hibernate Search 3.3.0.X

by Manik Surtani (JIRA)

Move Query Module to use Hibernate Search 3.3.0.X ------------------------------------------------- Key: ISPN-646 URL: https://jira.jboss.org/browse/ISPN-646 Project: Infinispan Issue Type: Task Components: Querying Reporter: Manik Surtani Assignee: Navin Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final At the time of this writing, Hibernate Search 3.3.0.Beta1 is available. Will need to test the query module accordingly after such an upgrade. https://repository.jboss.org/nexus/content/groups/public/org/hibernate/hi... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-670) Consider all entries from data container as eviction candidates

by Vladimir Blagojevic (JIRA)

Consider all entries from data container as eviction candidates --------------------------------------------------------------- Key: ISPN-670 URL: https://jira.jboss.org/browse/ISPN-670 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic There was a subtle change of eviction semantics starting with 4.1 where only immortal entries are considered as eviction candidates. By default all entries are immortal, that is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration !=-1 || lifespan !=-1) they are not subject to eviction policies and container size can grow above limit specified in maxEntries. This policy is confusing and it does not make a lot of sense. All candidates, both mortal and immortal should be considered as eviction candidates and as such subject to eviction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2010