[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1425) Incorrect settings [timeToLiveSeconds, maxIdleTimeSeconds] when default in REST

[Galder Zamarreño (JIRA)]

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

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

I can see what the problem is, but the solution is not right since it causes issues as shown by ISPN-732.

A better solution would be to replace the "case (0, 0, false)" match in putInCache() method by:

{code}case (x, y, false) if x <= 0 && y <=0 => cache.put(key, obj){code}

Can you give this a shot?

> Incorrect settings [timeToLiveSeconds,maxIdleTimeSeconds] when default in REST 
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-1425
>                 URL: https://issues.jboss.org/browse/ISPN-1425
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 5.1.0.ALPHA1
>            Reporter: Greg Autric
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.BETA2
>
>         Attachments: Server.scala.ISPN-1425.patch, Server.scala.ISPN-1425.v2.patch
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> If HTTP client didn't use 
> timeToLiveSeconds or/and maxIdleTimeSeconds in all PUT/POST header request
> Cache entry will allways use -1 for timeToLiveSeconds and -1 for maxIdleTimeSeconds
> instead of current Cache settings

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