[infinispan-issues] [JBoss JIRA] (ISPN-11212) Ensure max idle works with passivation

[Wolf-Dieter Fink (Jira)]

    [ https://issues.redhat.com/browse/ISPN-11212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955466#comment-13955466 ] 

Wolf-Dieter Fink commented on ISPN-11212:
-----------------------------------------

It seems working with local caches, only distributed/replicated are affected.
Configuration is like below.

If the entry is read by a simple get() it will drop after max-idle to a random number <"memory object size"
if the entry is read by getWithMetadata the entries are kept until lifespan is reached!

~~~
                <distributed-cache name="ExpirationCache" owners="2" mode="ASYNC" remote-timeout="25000" start="EAGER">
                    <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="20000" concurrency-level="1000"/>
                    <transaction mode="NONE"/>
                    <memory>
                        <object size="100"/>
                    </memory>
                    <expiration max-idle="20000" lifespan="300000"/>
                    <persistence passivation="true">
                        <file-store max-entries="1000000" relative-to="jboss.server.data.dir" path="api-general-filestore" name="api-general-filestore" shared="false" preload="false" fetch-state="true" purge="true"/>
                    </persistence>
                </distributed-cache>
~~~

> Ensure max idle works with passivation
> --------------------------------------
>
>                 Key: ISPN-11212
>                 URL: https://issues.redhat.com/browse/ISPN-11212
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Expiration, Loaders and Stores
>    Affects Versions: 10.1.1.Final
>            Reporter: Tristan Tarrant
>            Assignee: Will Burns
>            Priority: Major
>             Fix For: 11.0.0.Final
>
>
> We need to have tests in place that ensure that maxIdle expiration works in combination with passivation.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)