[JBoss JIRA] (ISPN-3202) Infinispan cachestores remove entries early when maxIdle used
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3202?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3202:
--------------------------------
Component/s: Loaders and Stores
> Infinispan cachestores remove entries early when maxIdle used
> -------------------------------------------------------------
>
> Key: ISPN-3202
> URL: https://issues.jboss.org/browse/ISPN-3202
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> 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: Pedro Ruivo
> 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
12 years, 2 months
[JBoss JIRA] (ISPN-3204) Implement Last-Modified header returned by REST endpoint correctly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3204?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3204:
--------------------------------
Labels: Server (was: )
> 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, 6.0.0.Final
> Reporter: Martin Gencur
> Assignee: Galder Zamarreño
> Labels: Server
>
> 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
12 years, 2 months
[JBoss JIRA] (ISPN-3203) Infinispan cache index not loading initial data
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3203?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3203:
--------------------------------
Component/s: Querying
> Infinispan cache index not loading initial data
> -----------------------------------------------
>
> Key: ISPN-3203
> URL: https://issues.jboss.org/browse/ISPN-3203
> Project: Infinispan
> Issue Type: Bug
> Components: Querying
> 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: Adrian Nistor
> 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
12 years, 2 months