[infinispan-issues] [JBoss JIRA] (ISPN-4950) Expiration settings not applied to entries stored via CLI

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-4950:
-----------------------------------
              Status: Pull Request Sent  (was: Coding In Progress)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/3055


> Expiration settings not applied to entries stored via CLI
> ---------------------------------------------------------
>
>                 Key: ISPN-4950
>                 URL: https://issues.jboss.org/browse/ISPN-4950
>             Project: Infinispan
>          Issue Type: Bug
>          Components: CLI, Remote Protocols, Server
>    Affects Versions: 7.0.0.Final
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 7.1.0.Alpha1, 7.1.0.Final
>
>
> Data stored via CLI does not seem to get container expiration settings applied. E.g.
> For a server side configuration like this:
> {code}
> <local-cache name="shay" start="EAGER">
>   <expiration lifespan="1000" max-idle="1000"/>
> </local-cache>
> {code}
> Storing it and retrieving it always returns the entry, no matter how long it's waited:
> {code}
> [disconnected /] connect
> [standalone at localhost:9990 /] cd subsystem=infinispan/cache-container=local
> [standalone at localhost:9990 cache-container=local] cache shay
> [standalone at localhost:9990 local-cache=shay] put a a1
> [standalone at localhost:9990 local-cache=shay] get a
> a1
> ...
> [standalone at localhost:9990 local-cache=shay] get a
> a1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)