February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3997: ----------------------------------------------- wfink(a)redhat.com changed the Status of [bug 1063768|https://bugzilla.redhat.com/show_bug.cgi?id=1063768] from NEW to CLOSED > Expired cache entries are not pruned from memory and store on access > -------------------------------------------------------------------- > > Key: ISPN-3997 > URL: https://issues.jboss.org/browse/ISPN-3997 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Remote HotRod access to infinispan-server > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration. > This will not be done if the key is access. > In case of having no scheduler to prune the entries this might cause OutOfMemory issues. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3997. --------------------------------- Resolution: Rejected we don't not remove the expired entry on access, but merely check to see if it has expired, and in that case return null. > Expired cache entries are not pruned from memory and store on access > -------------------------------------------------------------------- > > Key: ISPN-3997 > URL: https://issues.jboss.org/browse/ISPN-3997 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Remote HotRod access to infinispan-server > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration. > This will not be done if the key is access. > In case of having no scheduler to prune the entries this might cause OutOfMemory issues. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3997: ------------------------------------- Indeed the entries from memory (or persistent store for that matter) are not purged, if expired, during access. What actually happens is that we do check in callers thread to make sure that the entry is expired or not before returning it to the user[1]. The documentation should rather read: "if the user gets an entry that has been expired but not purged by the eviction thread yet, then null will be returned to the user. Note that this doesn't remove the entry from the grid yet, but this would happen when the eviction thread kicks in" [1] e.g. in the [JdbcStringBasedCacheStore|https://github.com/mmarkus/infinispan/blob/mast... ] > Expired cache entries are not pruned from memory and store on access > -------------------------------------------------------------------- > > Key: ISPN-3997 > URL: https://issues.jboss.org/browse/ISPN-3997 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Remote HotRod access to infinispan-server > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > > Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration. > This will not be done if the key is access. > In case of having no scheduler to prune the entries this might cause OutOfMemory issues. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4007) ReflectionUtil.findMethod returns wrong class name in exception

by Dennis Reed (JIRA)

Dennis Reed created ISPN-4007: --------------------------------- Summary: ReflectionUtil.findMethod returns wrong class name in exception Key: ISPN-4007 URL: https://issues.jboss.org/browse/ISPN-4007 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 6.0.1.Final Reporter: Dennis Reed Assignee: Dan Berindei ReflectionUtil#findMethod (both versions) recursively call up the superclass chain to look for a method until they get to Object or an interface. If the method is not found, the thrown exception will always be for java.lang.Object or the interface, instead of the actual class that was originally passed in. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4006) Make protostream OSGI/Karaf friendly by providing a features.xml

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4006: ----------------------------------- Summary: Make protostream OSGI/Karaf friendly by providing a features.xml Key: ISPN-4006 URL: https://issues.jboss.org/browse/ISPN-4006 Project: Infinispan Issue Type: Feature Request Components: Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Final -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3967) Create a feature file for HotRod client for easy installation in Karaf

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3967?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3967: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2387 > Create a feature file for HotRod client for easy installation in Karaf > ---------------------------------------------------------------------- > > Key: ISPN-3967 > URL: https://issues.jboss.org/browse/ISPN-3967 > Project: Infinispan > Issue Type: Feature Request > Reporter: Martin Gencur > Assignee: Martin Gencur > > A "feature" file is a descriptor of bundles required by a feature. (More info at http://icodebythesea.blogspot.cz/2012/03/making-osgi-deployments-easier-w...) > We should provide such a file for easy deployment on Karaf. Otherwise users will have to install all artifacts one by one (jboss-loggin, jgroups, infinispan-commons, infinispan-core, commons-pool, jboss-marshalling-osgi, ...) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3736) Backport to 5.2.x for EAP 6.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3736?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3736: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1036889|https://bugzilla.redhat.com/show_bug.cgi?id=1036889] from POST to MODIFIED > Backport to 5.2.x for EAP 6.3 > ----------------------------- > > Key: ISPN-3736 > URL: https://issues.jboss.org/browse/ISPN-3736 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 5.2.7.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > Fix For: 5.2.8.Final > > > This JIRA will track the issues that need to be backported to the 5.2.x branch for EAP 6.3. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4005) Upgrade to Protostream 1.0.0.Final

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4005?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4005: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to Protostream 1.0.0.Final > ---------------------------------- > > Key: ISPN-4005 > URL: https://issues.jboss.org/browse/ISPN-4005 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1 > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4005) Upgrade to Protostream 1.0.0.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4005?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4005: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2386 > Upgrade to Protostream 1.0.0.Final > ---------------------------------- > > Key: ISPN-4005 > URL: https://issues.jboss.org/browse/ISPN-4005 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1 > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4005) Upgrade to Protostream 1.0.0.Final

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4005: ----------------------------------- Summary: Upgrade to Protostream 1.0.0.Final Key: ISPN-4005 URL: https://issues.jboss.org/browse/ISPN-4005 Project: Infinispan Issue Type: Component Upgrade Components: Remote Querying Affects Versions: 6.0.1.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Alpha1 -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014