[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-203) PojoCache get/put/remove object apis needs to be atomic

Jason T. Greene (JIRA) jira-events at lists.jboss.org
Tue Sep 18 19:13:11 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBCACHE-203?page=all ]

Jason T. Greene updated JBCACHE-203:
------------------------------------

    Affects Version/s:     (was: PojoCache)

> PojoCache get/put/remove object apis needs to be atomic
> -------------------------------------------------------
>
>                 Key: JBCACHE-203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-203
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>             Fix For: 1.4.0.GA
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> In TreeCacheAop, there is a need for aotomic operation with get/put/remove-Object such that concurrent update of the same object is protected. E.g., if I do a removeObject(pojo) while another thread is doing pojo.setName(), can produce a race condition.
> Currently, it is done under an artificial tx context. We should re-factor this. 

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

        



More information about the jboss-jira mailing list