[
https://issues.jboss.org/browse/JBCACHE-1602?page=com.atlassian.jira.plug...
]
Dennis Reed commented on JBCACHE-1602:
--------------------------------------
The cause is in LegacyCacheLoaderInterceptor#loadNode:
if (n != null && !n.isDataLoaded())
{
if (trace) log.trace("Setting dataLoaded to true");
n.setDataLoaded(true);
}
With MVCC or Pessimistic locking, this is executed.
With Optimistic locking, n is null, so this is skipped.
NodeSPI.isDataLoaded is false for new node with optimistic locking
------------------------------------------------------------------
Key: JBCACHE-1602
URL:
https://issues.jboss.org/browse/JBCACHE-1602
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Cache loaders
Affects Versions: 3.2.5.GA
Reporter: Dennis Reed
Assignee: Dennis Reed
The following prints "true" with MVCC or Pessimistic locking, but
"false" with Optimistic.
cache.put ( fqn, key, test );
NodeSPI n = (NodeSPI)cache.getNode ( fqn );
System.out.println ( n.isDataLoaded() );
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira