[
http://jira.jboss.com/jira/browse/JBCACHE-674?page=comments#action_12339549 ]
Ben Wang commented on JBCACHE-674:
----------------------------------
One possible solution is when cacheB attach is replicated to cacheA, it will trigger a
proper higher level detach(oldValue) first. In this sense, the detach will repopulate the
in-memory copy and also detach the interceptors. Again, this will have to be configurable
since this can be expensive and most of the use cases focus on the passive update instead
of active one.
PojoCache to handle simultaneous pojo attach on the clustering nodes
--------------------------------------------------------------------
Key: JBCACHE-674
URL:
http://jira.jboss.com/jira/browse/JBCACHE-674
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: POJOCache
Original Estimate: 1 week
Remaining Estimate: 1 week
Currently we don't handle cases with active attachment of pojo on all clustering
nodes. For example,
cacheA.attach("1", pojo1);
cacheB.attach("1", pojo2);
pojo2 will overwrite pojo1 but pojo1 will still have cache interceptor attached to it. So
solution will have to be some sort of check dirty mechanism when any POJO operation is
called. But this will introduce more overheads.
Still need to gather more use case for 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