June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3205) Upgrade to JGroups 3.3.1.Final

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3205?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3205: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1884 > Upgrade to JGroups 3.3.1.Final > ------------------------------ > > Key: ISPN-3205 > URL: https://issues.jboss.org/browse/ISPN-3205 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 5.3.0.CR1 > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.CR2, 5.3.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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3205) Upgrade to JGroups 3.3.1.Final

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3205: ----------------------------------- Summary: Upgrade to JGroups 3.3.1.Final Key: ISPN-3205 URL: https://issues.jboss.org/browse/ISPN-3205 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 5.3.0.CR1 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.CR2, 5.3.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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3204) Implement Last-Modified header returned by REST endpoint correctly

by Martin Gencur (JIRA)

Martin Gencur created ISPN-3204: ----------------------------------- Summary: Implement Last-Modified header returned by REST endpoint correctly Key: ISPN-3204 URL: https://issues.jboss.org/browse/ISPN-3204 Project: Infinispan Issue Type: Bug Affects Versions: 5.3.0.CR1 Reporter: Martin Gencur Assignee: Galder Zamarreño Fix For: 6.0.0.Final As described in ISPN-3153, the Last-Modified HTTP header does not always return correct date/time of the last modification. The goal of this JIRA is to fix this behaviour. Explanation of the bug: "Since immortal entries never die, we don't track creation time for them. We don't wanna be doing that either cos it takes valuable space that's might only be relevant for REST. In fact, we don't have anything that maps directly to last-modified per se. For transient entries, we track when the entry was last used (read or write) and for mortal entries, we track the creation time, which is not necessarily last modified time. Last-modified returns the expected value only when timeToLiveSeconds has been set and we're tracking creation time (mortal entry)." -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2753: ---------------------------------- Description: staxmapper is composed of very few classes, of which we only use half. In order to minimize the number of dependencies, the logic of staxmapper can be incorporated in Infinispan, tailored to our own specific needs. was:staxmapper is composed of very few classes, of which we only use half. > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > staxmapper is composed of very few classes, of which we only use half. In order to minimize the number of dependencies, the logic of staxmapper can be incorporated in Infinispan, tailored to our own specific needs. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2753: ---------------------------------- Affects Version/s: (was: 5.2.0.CR2) > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > staxmapper is composed of very few classes, of which we only use half. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2753: ---------------------------------- Fix Version/s: 6.0.0.Alpha1 6.0.0.Final > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > staxmapper is composed of very few classes, of which we only use half. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2753) Drop the staxmapper dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2753?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reopened ISPN-2753: ----------------------------------- > Drop the staxmapper dependency > ------------------------------ > > Key: ISPN-2753 > URL: https://issues.jboss.org/browse/ISPN-2753 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.2.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > staxmapper is composed of very few classes, of which we only use half. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3203) Infinispan cache index not loading initial data

by Ralph Jennings (JIRA)

[ https://issues.jboss.org/browse/ISPN-3203?page=com.atlassian.jira.plugin.... ] Ralph Jennings updated ISPN-3203: --------------------------------- Environment: Linux: debian wheezy uname -a: Linux hostname 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux JBoss: 7.1.2.Final Embedded cache using infinispan 5.2.6.Final jars included in WAR's WEB-INF/lib directory. > Infinispan cache index not loading initial data > ----------------------------------------------- > > Key: ISPN-3203 > URL: https://issues.jboss.org/browse/ISPN-3203 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.6.Final > Environment: Linux: debian wheezy > uname -a: Linux hostname 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux > JBoss: 7.1.2.Final > Embedded cache using infinispan 5.2.6.Final jars included in WAR's WEB-INF/lib directory. > Reporter: Ralph Jennings > Assignee: Mircea Markus > Labels: cache-store, index, infinispan, preload > > If you create a cache with an existing store to preload data from, the data is available to the cache (get and keySet works) but not to the index (no cache queries work). > Only entries put into the cache after it starts up can be seen by the index. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3203) Infinispan cache index not loading initial data

by Ralph Jennings (JIRA)

Ralph Jennings created ISPN-3203: ------------------------------------ Summary: Infinispan cache index not loading initial data Key: ISPN-3203 URL: https://issues.jboss.org/browse/ISPN-3203 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.6.Final Reporter: Ralph Jennings Assignee: Mircea Markus If you create a cache with an existing store to preload data from, the data is available to the cache (get and keySet works) but not to the index (no cache queries work). Only entries put into the cache after it starts up can be seen by the index. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3202) Infinispan cachestores remove entries early when maxIdle used

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3202?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated ISPN-3202: --------------------------------------- Forum Reference: https://community.jboss.org/message/821408#821408, https://community.jboss.org/thread/229004 (was: https://community.jboss.org/thread/229004) > Infinispan cachestores remove entries early when maxIdle used > ------------------------------------------------------------- > > Key: ISPN-3202 > URL: https://issues.jboss.org/browse/ISPN-3202 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.6.Final > Environment: Linux: debian wheezy > uname -a: Linux hostname 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux > JBoss: 7.1.2.Final > Embedded cache using infinispan 5.2.6.Final jars included in WAR's WEB-INF/lib directory. > Reporter: Ralph Jennings > Assignee: Mircea Markus > Labels: cache-store, maxIdle, timeout > > When adding an entry to the cache (embedded), specifying maxIdle... The entry goes into the store, but the store removes the entry when maxIdle time elapses from creation (rather than from last access). > The cache correctly keeps the entry in memory (unless evicted). > This leaves the cache and store out of sync. > I saw this same behavior with both stringKeyedJdbcStore and fileStore. -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013