October 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-730) A DefaultSharedExecutorFactory is needed

by Manik Surtani (JIRA)

A DefaultSharedExecutorFactory is needed ---------------------------------------- Key: ISPN-730 URL: https://jira.jboss.org/browse/ISPN-730 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani ... which uses a common executor for all caches in a cache manager. This should be the default executor factory used, to prevent multiple eviction threads, etc., one for each cache in a cache manager. -- 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 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-732) In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be -1

by Galder Zamarreño (JIRA)

In REST, default values for maxIdleTimeSeconds and timeToLiveSeconds should be -1 --------------------------------------------------------------------------------- Key: ISPN-732 URL: https://jira.jboss.org/browse/ISPN-732 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final, 4.0.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1 Default values for maxIdleTimeSeconds and timeToLiveSeconds params in REST server should be -1. Otherwise default values are 0 which can lead to immediate removal. -- 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 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-609) Make the JGroupsTRansport Listenable

by craig bomba (JIRA)

Make the JGroupsTRansport Listenable ------------------------------------ Key: ISPN-609 URL: https://jira.jboss.org/browse/ISPN-609 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: craig bomba Assignee: craig bomba Priority: Minor We needed to make the JGroupsTransport listenable. We needed events for detecting that a merge has taken place org.infinispan.factories.EmptyConstructorFactory Just added JGroupsTransportNotifier.class to the @DefaultFactoryFor annotation. org.infinispan.notifications.jgroupstransport.JGroupsTransportNotifier Interface for the JGroupsTransportNotifier notifier. org.infinispan.notifications.jgroupstransport.JGroupsTransportNotifierImpl The JGroupsTransportNotifier notifier implementation. Supports events for a merge. org.infinispan.notifications.jgroupstransport.annotation.MergeViewAccepted The bare annotations to add to JGroupsTransport listeners. org.infinispan.notifications.jgroupstransport.event.Event The interface for the merge view accepted event implementations. org.infinispan.notifications.replicationqueuelistener.event.MergeViewAcceptedEvent The event implementations. org.infinispan.transport.Transport Updated to implement listenable. org.infinispan.transport.jgroups.JGroupsTransport Updated to throw an event when a merge view is accepted. -- 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 months

3
13
0 / 0

[JBoss JIRA] Created: (ISPN-705) NamespaceFilter.ISPN_NS does not match published schema

by Paul Ferraro (JIRA)

NamespaceFilter.ISPN_NS does not match published schema ------------------------------------------------------- Key: ISPN-705 URL: https://jira.jboss.org/browse/ISPN-705 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.2.0.ALPHA3 Reporter: Paul Ferraro Assignee: Manik Surtani NamespaceFilter.ISPN_NS constant defines the namespace expected by JAXB parsing. The current value, "urn:infinispan:config:4.1" does not match the namespace defined in the schema itself published at: http://infinispan.org/schemas/infinispan-config-4.2.xsd -- 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 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-698) DB2 - SQL Parameterization issue on FETCH FIRST ? clause

by Franck Garcia (JIRA)

DB2 - SQL Parameterization issue on FETCH FIRST ? clause -------------------------------------------------------- Key: ISPN-698 URL: https://jira.jboss.org/browse/ISPN-698 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.Final Environment: linux ubuntu 10.04 x386 32 bits hot spot jvm 1.6_018 DB2/400 (jdbc jtopen v 7.1) Reporter: Franck Garcia Assignee: Manik Surtani When trying to pre-load a cache from a jdbc db2 store, infinispan takes the maxEntries parameter of the eviction config to limit the number of rows fetched from the db. SELECT DATA_COLUMN, ID_COLUMN FROM MY_LUCENE_IDX_luceneIndex FETCH FIRST ? ROWS ONLY Unfortunatelly db2 seems to not accept SQL parameterization for the FETCH FIRST x CLAUSE java.sql.SQLException: [SQL0104] Token ? was not valid. Valid tokens: ROW ROWS. Cause . . . . . : A syntax error was detected at token ?. Token ? is not a valid token. A partial list of valid tokens is ROW ROWS. -- 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 months

4
9
0 / 0

[JBoss JIRA] Updated: (ISPN-180) Colocated nodes should be handled in DIST

by Mircea Markus (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Mircea Markus updated ISPN-180: ------------------------------- Fix Version/s: 4.2.0.BETA1 (was: 4.2.0.ALPHA4) > Colocated nodes should be handled in DIST > ----------------------------------------- > > Key: ISPN-180 > URL: https://jira.jboss.org/browse/ISPN-180 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Blocker > Fix For: 4.2.0.BETA1, 4.2.0.Final > > > DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-691) ReplicationQueue has an out-of-order issue

by craig bomba (JIRA)

ReplicationQueue has an out-of-order issue ------------------------------------------ Key: ISPN-691 URL: https://jira.jboss.org/browse/ISPN-691 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 4.2.0.ALPHA2, 4.2.0.ALPHA1, 4.1.0.Final Reporter: craig bomba Assignee: craig bomba The ReplicationQueue has an exposure to distributing items out of order. The ReplicationQueue may flush items in either of 2 ways. One way is the background thread provided by a ThreadPoolExecutor flushing on a timer. The other is via the current thread that does a put (which calls ReplicationQueue.add). In the case of the call to add if it hits the max size (set in the config by replQueueMaxElements) then items may get flushed to other nodes out of order. This is not evident when a test case only includes puts (new items or updated items in a cache). Your test must include removals to expose this concern. -- 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 months

2
15
0 / 0

[JBoss JIRA] Created: (ISPN-725) Config validator should not allow a replication queue to be defined with DIST

by Manik Surtani (JIRA)

Config validator should not allow a replication queue to be defined with DIST ----------------------------------------------------------------------------- Key: ISPN-725 URL: https://jira.jboss.org/browse/ISPN-725 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Priority: Minor Fix For: 4.2.0.BETA1, 4.2.0.Final Needs a unit test as well -- 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 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-726) Default cluster mode and transaction mgr lookup should be used if not specified in the <clustering /> and <transaction /> tags

by Manik Surtani (JIRA)

Default cluster mode and transaction mgr lookup should be used if not specified in the <clustering /> and <transaction /> tags ------------------------------------------------------------------------------------------------------------------------------ Key: ISPN-726 URL: https://jira.jboss.org/browse/ISPN-726 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Priority: Minor Fix For: 4.2.0.BETA1, 4.2.0.Final The transaction tag *requires* you to specify the transactionManagerLookupClass, even though a sensible default (GenericTransactionManagerLookup) can be used. The same goes for <clustering /> which should default to DIST_SYNC. -- 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 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-709) integrate with JGroups 2.10.1

by Mircea Markus (JIRA)

integrate with JGroups 2.10.1 ----------------------------- Key: ISPN-709 URL: https://jira.jboss.org/browse/ISPN-709 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.2.0.BETA1 Integrate with jgroups 2.10.1. Also test the new FD protocol and make sure our default configs ship with the improved version: https://jira.jboss.org/browse/JGRP-1236 -- 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 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2010