[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1285) Cache entries stored via Hot Rod client with default expiry remain in cache

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-1285:
----------------------------------------

I agree that this is not intuitive (it's not even symmetric!), and it's like this cos it was not designed with this use case in mind. What I explained above is what the code looks like today, and it's too late to change it right now since it's part of the REST protocol. 

In the same way that we have a JIRA for a second version of the Hot Rod protocol, we need a JIRA for the 2nd version of the REST protocol where this kind of stuff can be tightened. It'd need some investigation to see how to accomodate different REST protocol versions.

Exactly, the documentation does not say anything cos no one has looked into this until now and hence I had not yet had time to change the docu to show this :). That's precisely what I'm planning to do once I've committed a unit test that verifies the current behaviour. 

> Cache entries stored via Hot Rod client with default expiry remain in cache
> ---------------------------------------------------------------------------
>
>                 Key: ISPN-1285
>                 URL: https://issues.jboss.org/browse/ISPN-1285
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.0.0.CR8
>            Reporter: Martin Gencur
>            Assignee: Galder Zamarreño
>             Fix For: 5.0.0.FINAL
>
>
> Default values for expiration specified via Infinispan configuration file (tag <expiration lifespan="2000" maxIdle="1000" />) do not influence real lifespan of cache entries stored via the Hot Rod client.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira