]
Mircea Markus commented on JBCACHE-1365:
----------------------------------------
org.jboss.cache.commands.StructuralNodesOnRollbackTest - UT to reproduce the issue on all
scenarios (it is not only on putDataMap...)
rollback does not removes the nodes created for locking
-------------------------------------------------------
Key: JBCACHE-1365
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1365
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.GA
Reporter: Mircea Markus
Assigned To: Manik Surtani
Priority: Critical
Fix For: 2.2.0.GA
within a Tx: when adding a new k,v pair to an *inexistent* node, the supporting tree
structure is created within the transaction. This supporting (intermediate node to the
final one) tree structure does not get deleteted on Rollback.
e.g.
public void testPutDataMap() throws Exception
{
HashMap map = new HashMap();
map.put("k","v");
assert !cache.exists("/a/b");
txMgr.begin();
cache.put("/a/b/c", map);
assert cache.exists("/a/b");
txMgr.rollback();
assert !cache.exists("/a/b");
}
solution: nodes are being create in PessimisticLockInterceptor, they should be passed in
to the command itself so that it will be aware of them at rollback time, and it will
remove them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: