[
http://jira.jboss.com/jira/browse/JBCACHE-833?page=all ]
Manik Surtani closed JBCACHE-833.
---------------------------------
Resolution: Rejected
And the lock interceptor does do this; the lock method is passed up the interceptor chain.
The reason it is done here is to prevent a race condition between when a node is evicted
versus reloaded.
Redundant lock in cache loader
------------------------------
Key: JBCACHE-833
URL:
http://jira.jboss.com/jira/browse/JBCACHE-833
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.0.SP1, 1.4.0.GA
Reporter: Ben Wang
Assigned To: Manik Surtani
Priority: Minor
Fix For: 2.0.0.GA
Currently in CacheLoader, it calls "lock" from loadIfNeeded method. The
"lock" method in turns invokes
TreeCache.java
public void _lock(Fqn fqn, DataNode.LockType lock_type, boolean recursive)
throws TimeoutException, LockingException
{
log.warn("method _lock() should not be invoked on TreeCache");
}
I think the LockInterceptor should take care of the locking properly. So this call should
be deprecated.
--
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