[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-111) InternalEntryFactory mixing up lifespan and created for MortalCacheValue

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Fri Jun 19 12:42:56 EDT 2009


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

Galder Zamarreno resolved ISPN-111.
-----------------------------------

    Resolution: Done


> InternalEntryFactory mixing up lifespan and created for MortalCacheValue
> ------------------------------------------------------------------------
>
>                 Key: ISPN-111
>                 URL: https://jira.jboss.org/jira/browse/ISPN-111
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 4.0.0.ALPHA5
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.BETA1
>
>
> For MortalCacheValue, InternalEntryFactory.createValue(Object, long, long, long , long) was doing the following:
> if (lifespan > -1 && maxIdle < 0) return new MortalCacheValue(v, lifespan, created);
> But the MortalCacheValue constructor was like this:
>    MortalCacheValue(Object value, long created, long lifespan) {
>       super(value);
>       this.created = created;
>       this.lifespan = lifespan;
>    }
> So that factory method was mixing up created and lifespan 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

        



More information about the infinispan-issues mailing list