July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2758) HTTP session management for any App Server / Servlet Container

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2758?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2758: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > HTTP session management for any App Server / Servlet Container > -------------------------------------------------------------- > > Key: ISPN-2758 > URL: https://issues.jboss.org/browse/ISPN-2758 > Project: Infinispan > Issue Type: Feature Request > Environment: Any App Server / Servlet container > Reporter: Lucas Ponce > Assignee: Mircea Markus > > allows to add Infinispan to manage Http sessions in App Servers or Servlet Containers for wider cluster scenarios. -- 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-2445) Gracefull shutdown - transfer data to other nodes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2445?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2445: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Gracefull shutdown - transfer data to other nodes > ------------------------------------------------- > > Key: ISPN-2445 > URL: https://issues.jboss.org/browse/ISPN-2445 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Matej Lazar > Assignee: Mircea Markus > > Distributed cache should provide an configuration option to block shutdown until data from shutting down node is transferred to other nodes. > This feature is useful if Infinispan is used as persistent storage. > Without this option, in a cloud environment, where server node is deleted on scale down event, users are forced to use external storage, if they don't want to loose data. -- 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-1219) Add support for incremental optimistic locking

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1219?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1219: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Add support for incremental optimistic locking > ---------------------------------------------- > > Key: ISPN-1219 > URL: https://issues.jboss.org/browse/ISPN-1219 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: deadlock, deadlock_detection > > This feature is fully described here: http://community.jboss.org/wiki/IncrementalOptimisticLocking > This together with lock reordering[1] cover 100% of the possible deadlock situations in the optimistic locking scheme[2]. > [1] http://community.jboss.org/wiki/LockReorderingForAvoidingDeadlocks > [2] http://community.jboss.org/wiki/OptimisticLockingInInfinispan -- 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-127) Ability to bring up/take down nodes based on SLAs

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-127?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-127: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Ability to bring up/take down nodes based on SLAs > ------------------------------------------------- > > Key: ISPN-127 > URL: https://issues.jboss.org/browse/ISPN-127 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Manik Surtani > Assignee: Manik Surtani > > Need to look at what JOPR can provide by way of bringing up or killing instances based on overall load. Perhaps other metrics such as time of day could be used as well. Would be very useful to help build out a truly 'elastic' data grid. -- 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-1068) Add usage support similar to the one included in Spring Data

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1068?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1068: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Add usage support similar to the one included in Spring Data > ------------------------------------------------------------ > > Key: ISPN-1068 > URL: https://issues.jboss.org/browse/ISPN-1068 > Project: Infinispan > Issue Type: Feature Request > Components: Spring integration > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > > ... i.e. InfinispanTemplate/InfinispanCallback -- 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-1762) Add tests for configuration options that can change at runtime

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1762?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1762: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Add tests for configuration options that can change at runtime > -------------------------------------------------------------- > > Key: ISPN-1762 > URL: https://issues.jboss.org/browse/ISPN-1762 > Project: Infinispan > Issue Type: Task > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Manik Surtani > > There are no test for those configuration options that can be changed at runtime. -- 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-1149) Allow HotRodServer to obtain its own port

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1149?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1149: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Allow HotRodServer to obtain its own port > ----------------------------------------- > > Key: ISPN-1149 > URL: https://issues.jboss.org/browse/ISPN-1149 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 5.0.0.FINAL > Reporter: Jeff Ramsdale > Assignee: Manik Surtani > > When embedding a HotRodServer in my application I want to be able to start multiple instances on the same machine without having to track a pool of ports. HotRodServer should have an option to start up and obtain its own port, which I can then provide to my clients. In this fashion port bind collisions will not occur. -- 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-1495) Implement a GlusterFS store to be used as a CacheLoader

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1495?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1495: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Implement a GlusterFS store to be used as a CacheLoader > ------------------------------------------------------- > > Key: ISPN-1495 > URL: https://issues.jboss.org/browse/ISPN-1495 > Project: Infinispan > Issue Type: Feature Request > Reporter: Sanne Grinovero > Assignee: Manik Surtani > -- 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-263) Handle JGroups MERGE events to help deal with split brains

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-263?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-263: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Handle JGroups MERGE events to help deal with split brains > ---------------------------------------------------------- > > Key: ISPN-263 > URL: https://issues.jboss.org/browse/ISPN-263 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Manik Surtani > Labels: MERGE, split_brain > > JGroups already detects split brains and issues a callback. The cache layer needs to decide what to do. The idea is to implement a few canned policies (restart, wipe, etc) and allow custom handlers to be attached as well. > Analogous to JBCACHE-471 -- 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-1833) Add EmbeddedCacheManager.getGlobalComponentRegistry

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1833?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-1833: ------------------------------------- +1 as the cache.getAdvancedCache().getComponentRegistry() requires a cache to be up and running. > Add EmbeddedCacheManager.getGlobalComponentRegistry > --------------------------------------------------- > > Key: ISPN-1833 > URL: https://issues.jboss.org/browse/ISPN-1833 > Project: Infinispan > Issue Type: Enhancement > Components: Core API > Reporter: Galder Zamarreño > Assignee: Manik Surtani > Fix For: 6.0.0.Final > > > You should be able to retrieve the global component registry out of the EmbeddedCacheManager. > Rather that having to do: > cache.getAdvancedCache().getComponentRegistry().getGlobalComponentRegistry() -- 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