[
http://jira.jboss.com/jira/browse/JBCACHE-718?page=all ]
Jason T. Greene resolved JBCACHE-718.
-------------------------------------
Resolution: Won't Fix
Any update will trigger a lock, so the remove is not needed. However in the future it
might be possible to have a replicated read with forceWriteLock = true
PojoCache TxLockInterceptor needs to release the lock node as well
------------------------------------------------------------------
Key: JBCACHE-718
URL:
http://jira.jboss.com/jira/browse/JBCACHE-718
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Jason T. Greene
Priority: Minor
Fix For: 2.1.0.GA
Currently, in TxLockInterceptor, I achieve the node lock by applying explicitly a
cache.put(). It has two drawbacks:
1) It explicit going to insert a value to that node
2) Needs to do a remove when it is done.
Not much can be done re: 1 now, but we should do 2, alhtough it will degrade the
performance further.
--
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