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

[Jakub Markos (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145887#comment-13145887 ] 

Jakub Markos commented on ISPN-3202:
------------------------------------

It doesn't seem that this issue is solvable without updating the metadata of the entry in the cachestore for each get (which would be slow). So maybe we could at least warn the users in the documentation against using maxIdle with cachestores?

> 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 was sent by Atlassian JIRA
(v6.4.11#64026)