July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1935) Provide tree cache specific listener callbacks

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1935?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1935: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Provide tree cache specific listener callbacks > ---------------------------------------------- > > Key: ISPN-1935 > URL: https://issues.jboss.org/browse/ISPN-1935 > Project: Infinispan > Issue Type: Enhancement > Components: Core API, Tree API > Affects Versions: 5.1.2.FINAL > Reporter: Michael Gronau > Assignee: Galder Zamarreño > Labels: API, CacheEntryModified, Notifications, TreeCache > Attachments: TreeListenerTest.java > > > A put operation to the TreeCache API causes multiple CacheEntryModified events to be fired. The data map (an AtomicHashMap) is always empty and does not contain the modifications. The notifications are fired twice for isPre=false and isPre=true, which means they are fired 4 times. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3209) Server operation to suppress state transfer

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3209?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3209: ------------------------------------- workaround: connect to the server nodes directly through JMX. > Server operation to suppress state transfer > ------------------------------------------- > > Key: ISPN-3209 > URL: https://issues.jboss.org/browse/ISPN-3209 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 5.2.6.Final > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > This issue is to provide a Server operation for the functionality implemented in ISPN-3140 -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3070) Server protocol tests should also test against loaders/stores

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3070?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3070: -------------------------------- Priority: Minor (was: Major) > Server protocol tests should also test against loaders/stores > ------------------------------------------------------------- > > Key: ISPN-3070 > URL: https://issues.jboss.org/browse/ISPN-3070 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores, Remote protocols, Test Suite > Affects Versions: 5.3.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.Final > > > We need server tests which use loaders/stores -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1437) Servers need typed configuration and injection of components

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1437?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1437: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Servers need typed configuration and injection of components > ------------------------------------------------------------ > > Key: ISPN-1437 > URL: https://issues.jboss.org/browse/ISPN-1437 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Currently Infinispan servers cannot be plugged with executor services for the Netty master and worker threads, which makes them hard to manage in an app server environment where the app server might want to provide its own executors. > This might also require re-thinking how Infinispan servers are configured which currently rely on a bunch of properties. A typed approach would be welcome here. > In Lisbon, we had an interesting discussion around this but in the context of Infinispan core itself, how this is configured, how it has components injected that might be managed by an app server. He has some ideas based on the work he did for Weld, so maybe these can be applied to Infinispan servers too. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1627) Remove the deprecated OverrideDefault annotation

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1627?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1627: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Remove the deprecated OverrideDefault annotation > ------------------------------------------------ > > Key: ISPN-1627 > URL: https://issues.jboss.org/browse/ISPN-1627 > Project: Infinispan > Issue Type: Task > Components: CDI integration > Affects Versions: 5.1.0.CR1 > Reporter: Kevin Pollet > Assignee: Kevin Pollet > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3209) Server operation to suppress state transfer

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3209?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3209: -------------------------------- Priority: Minor (was: Major) > Server operation to suppress state transfer > ------------------------------------------- > > Key: ISPN-3209 > URL: https://issues.jboss.org/browse/ISPN-3209 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 5.2.6.Final > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > This issue is to provide a Server operation for the functionality implemented in ISPN-3140 -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-330) Separate scheduled/unscheduled async cache store configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-330?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-330: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Separate scheduled/unscheduled async cache store configuration > -------------------------------------------------------------- > > Key: ISPN-330 > URL: https://issues.jboss.org/browse/ISPN-330 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Implement configuration that allows differentiation between scheduled/unscheduled strategies: > <async enabled="true"> > <scheduled frequency="1000" /> > </async> > > <async enabled="true"> > <unscheduled poolsize="50" /> > </async> > > This format allows for easier extension of properties in scheduled/unscheduled modes. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2797) Support Query on Caches configured with INVALIDATION mode

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2797?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2797: --------------------------------------- Agreed, this might not make sense. I think a good resolution would be to validate the configuration against such case: throw a meaningfull error when indexing is enabled on an invalidating cache. > Support Query on Caches configured with INVALIDATION mode > --------------------------------------------------------- > > Key: ISPN-2797 > URL: https://issues.jboss.org/browse/ISPN-2797 > Project: Infinispan > Issue Type: Feature Request > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > This is currently not supported as other nodes won't get a copy of the value, and are consequentially unable to scan annotations or recognize new services which need to be started. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2679) Security needs to be implemented for memcache interface

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2679?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2679: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Security needs to be implemented for memcache interface > ------------------------------------------------------- > > Key: ISPN-2679 > URL: https://issues.jboss.org/browse/ISPN-2679 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Server > Reporter: Joel Tosi > Assignee: Mircea Markus > Labels: security > > Breakdown from ISPN-143 - https://issues.jboss.org/browse/ISPN-143 > We need to have security implemented in the memcache interface -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-224) Separate Cache metrics into different subservices in Jopr

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-224?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-224: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Separate Cache metrics into different subservices in Jopr > --------------------------------------------------------- > > Key: ISPN-224 > URL: https://issues.jboss.org/browse/ISPN-224 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > The current Jopr plugin shows a Cache with different metrics for each individual metric available in the cache, i.e. cache stores, cache loades, average repl time...etc. > This set up was fine when there was only a handful of metrics, but we after adding all the different managed attributes, we have around ~43 metrics now (some obviously but not always be present, i.e. metrics related to cache stores, deadlock detecting manager...etc), but they still appear but with no metrics at all. > So, as the number of metrics increase, you have a massive list of different values under Cache. > I think it'd be good to separate attributes from different interceptors into different services under Cache, i.e Statistics, Cache Store, Passivation/Activation...etc. > This would make it cleaner to read to the user. -- 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

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013