July 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-528) replace(K key, V value, long lifespan, TimeUnit unit) does not extend lifespan

by Michal Szymanski (JIRA)

replace(K key, V value, long lifespan, TimeUnit unit) does not extend lifespan ------------------------------------------------------------------------------ Key: ISPN-528 URL: https://jira.jboss.org/browse/ISPN-528 Project: Infinispan Issue Type: Bug Components: Eviction Environment: Windows, Tomcat, Axis Reporter: Michal Szymanski Assignee: Manik Surtani Fix For: 4.1.0.Final In our system we make something like this: tokenCache.put(tokenStr, token, 60 , TimeUnit.SECONDS); after let say 59seconds we call Token token = tokenCache.get(tokenStr); // where tokenCache is infinispan cache ... token.setValidTill(tokenTime); // some modfication of values of token tokenCache.replace(tokenStr, token, 60 , TimeUnit.SECONDS); As I understand from JAvaDoc: V replace(K key, V value, long lifespan, TimeUnit unit) replace object in cache = put token once again and in our exapmple object should live 60s more from time we call replace. But from my test when I call replace after 59s after initial 'put' object are removed in 60 second. When I call tokenCache.replace(tokenStr, token, 120 , TimeUnit.SECONDS); object lives 120s from initial put. Is it proper behaviour? If yes how to extend life of object by 60s = how to add 60s to lifespan? -- 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

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-511) The Expiration Algorithms have an unexpected way to manage the parameter maxEntries

by Nicolas Filotto (JIRA)

The Expiration Algorithms have an unexpected way to manage the parameter maxEntries ----------------------------------------------------------------------------------- Key: ISPN-511 URL: https://jira.jboss.org/browse/ISPN-511 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 4.1.0.BETA2, 4.0.0.Final Reporter: Nicolas Filotto Assignee: Manik Surtani The cache size should not exceed the value of the parameter maxEntries however in practice it does. See more details at http://community.jboss.org/message/549731. The Test Case has been added. -- 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

13 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-513) hotrod client:optimize serialization of key/values

by Mircea Markus (JIRA)

hotrod client:optimize serialization of key/values -------------------------------------------------- Key: ISPN-513 URL: https://jira.jboss.org/browse/ISPN-513 Project: Infinispan Issue Type: Feature Request Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 At the moment the keys and values are being serialized into an byte[] before being send over the wire. For the values, the serialization is possible when writing data over the wire, in the socket's output stream (instead of doing it before and keeping it in an byte[]). This should reduce the noise of creating too many byte[]. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Commented: (ISPN-24) JPA-like interface to Infinispan

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-24?page=com.atlassian.jira.plugin.syst... ] Manik Surtani commented on ISPN-24: ----------------------------------- Original design docs: http://community.jboss.org/wiki/DesignofJPA-likeAPIandNewFineGrainedrepli... > JPA-like interface to Infinispan > -------------------------------- > > Key: ISPN-24 > URL: https://jira.jboss.org/browse/ISPN-24 > Project: Infinispan > Issue Type: Feature Request > Components: Fine-grained API > Reporter: Manik Surtani > Assignee: Emmanuel Bernard > Priority: Blocker > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A replacement for POJO Cache, to provide fine-grained replication. > But also to provide a familiar API which folks can use to migrate stuff off traditional DB-centric apps. > Would use Infinispan AtomicMaps under the covers. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-24) JPA-like interface to Infinispan

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-24?page=com.atlassian.jira.plugin.syst... ] Manik Surtani updated ISPN-24: ------------------------------ Assignee: Emmanuel Bernard (was: Manik Surtani) Priority: Blocker (was: Major) @Emmanuel: Assigning this to you since you're driving most of the research behind this at the moment. > JPA-like interface to Infinispan > -------------------------------- > > Key: ISPN-24 > URL: https://jira.jboss.org/browse/ISPN-24 > Project: Infinispan > Issue Type: Feature Request > Components: Fine-grained API > Reporter: Manik Surtani > Assignee: Emmanuel Bernard > Priority: Blocker > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A replacement for POJO Cache, to provide fine-grained replication. > But also to provide a familiar API which folks can use to migrate stuff off traditional DB-centric apps. > Would use Infinispan AtomicMaps under the covers. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-39) Distributed executors

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-39?page=com.atlassian.jira.plugin.syst... ] Manik Surtani updated ISPN-39: ------------------------------ Assignee: Vladimir Blagojevic Priority: Critical (was: Major) > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://jira.jboss.org/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-186) Smart L1 cache invalidation

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.sys... ] Manik Surtani updated ISPN-186: ------------------------------- Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.0.0.BETA1) (was: 5.0.0.Final) > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://jira.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-515) Create Infinispan core architecture docs on wiki

by Manik Surtani (JIRA)

Create Infinispan core architecture docs on wiki ------------------------------------------------ Key: ISPN-515 URL: https://jira.jboss.org/browse/ISPN-515 Project: Infinispan Issue Type: Task Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.CR1 Lots of people have asked for this, plus it helps with contributions -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-525) Consider shipping log4j jar in root lib/ directory

by Galder Zamarreno (JIRA)

Consider shipping log4j jar in root lib/ directory -------------------------------------------------- Key: ISPN-525 URL: https://jira.jboss.org/browse/ISPN-525 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Manik Surtani Fix For: 4.1.0.CR1 Look into adding a log4 jar to root lib/ directory in distribution in order for modifications to etc/log4j.xml to have immediate effect. If log4j jar cannot be found, Infinispan uses JDK logging by default and it's not very obvious that a log4j jar is missing and that's why log4j.xml changes have no impact. This happens with any modules executed except: gui, ec2 and lucene-directory modules. These modules don't have this issue cos they ship a log4 jar: ./modules/ec2/lib/log4j-1.2.14.jar ./modules/gui/lib/log4j-1.2.14.jar ./modules/lucene-directory-demo/lib/log4j-1.2.14.jar -- 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-521) Remove the single_jar distribution archive

by Manik Surtani (JIRA)

Remove the single_jar distribution archive ------------------------------------------ Key: ISPN-521 URL: https://jira.jboss.org/browse/ISPN-521 Project: Infinispan Issue Type: Task Affects Versions: 4.1.0.BETA2 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final Unnecessary, and causes all sorts of issues with conflicts in certain deployments. -- 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

13 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2010