[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-113) InternalEntryFactory mixing up maxIdle, lastUsed and and created for TransientMortalCacheValue

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno resolved ISPN-113.
-----------------------------------

    Resolution: Done


> InternalEntryFactory mixing up maxIdle, lastUsed and and created for TransientMortalCacheValue
> ----------------------------------------------------------------------------------------------
>
>                 Key: ISPN-113
>                 URL: https://jira.jboss.org/jira/browse/ISPN-113
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.0.0.ALPHA5
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.BETA1
>
>
> For TransientMortalCacheValue, InternalEntryFactory.createValue(Object, long, long, long , long) was doing the following:
> return new TransientMortalCacheValue(v, maxIdle, lifespan, lastUsed, created);
> But the TransientMortalCacheValue constructor was like this:
>    TransientMortalCacheValue(Object value, long created, long lifespan, long maxIdle, long lastUsed) {
>       this(value, created, lifespan, maxIdle);
>       this.lastUsed = lastUsed;
>    }
> So that factory method was mixing up maxIdle, lastUsed and and created values.
> JBMAR externalizer implementations uses this factory method and hence when testing it, the issue arised.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira