[infinispan-issues] [JBoss JIRA] (ISPN-5664) Null is returned for a not expired entry in Hot Rod client

RH Bugzilla Integration (JIRA) issues at jboss.org
Wed Aug 19 23:08:33 EDT 2015


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

RH Bugzilla Integration commented on ISPN-5664:
-----------------------------------------------

Dave Stahl <dstahl at redhat.com> changed the Status of [bug 1243671|https://bugzilla.redhat.com/show_bug.cgi?id=1243671] from MODIFIED to ON_QA

> Null is returned for a not expired entry in Hot Rod client
> ----------------------------------------------------------
>
>                 Key: ISPN-5664
>                 URL: https://issues.jboss.org/browse/ISPN-5664
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote Protocols
>    Affects Versions: 8.0.0.Beta2
>            Reporter: William Burns
>            Assignee: William Burns
>             Fix For: 8.0.0.CR1, 7.2.5.Final
>
>
> For a mortal entry (lifespan > -1), overwriting it with lifespan=-1 (make it immortal) unexpectedly removes the entry like follows.
> ~~~
>     cache.put(key, "value1", 100, TimeUnit.SECONDS, 100, TimeUnit.SECONDS);
>     cache.get(key); // returns "value1"
>     cache.put(key, "value2", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS);
>     cache.get(key); // returns null, expected "value2"
>     cache.put(key, "value3", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS);
>     cache.get(key); // returns "value3"
> ~~~
> In library mode, the 2nd get returns non-null as expected.  The same behaviour is observed for a transient (maxIdle > -1) entry also.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the infinispan-issues mailing list