Readding a node deleted via a parent node causes lock timeout ------------------------------------------------------------- Key: JBCACHE-1405 URL: https://jira.jboss.org/jira/browse/JBCACHE-1405 Project: JBoss Cache Issue Type: Bug Security Level: Public(Everyone can see) Components: Transactions Affects Versions: 2.1.1.GA Reporter: Krzysztof Sobolewski Assignee: Manik Surtani Fix For: 3.0.0.GA Attachments: CacheTest.java Everything happens in the same transaction. Lets say we have a node /a/b/c. When I remove node /a, all three nodes (up to c) are marked as deleted. When I add node c again under the same path, I get a lock timeout on this node (with not really detailed message). From what I gather, the nodes are marked deleted just fine, but one detail is missing: they are not added as deleted in current transaction (except /a, which I delete explicitly). The removed root is added but its children are not. This causes a failure because PessimisticLockInterceptor.manageReverseRemove() checks whether the node is marked as deleted and whether it is marked as deleted in the current transaction. The latter test fails for /a/b.

Readding a node deleted via a parent node causes lock timeout ------------------------------------------------------------- Key: JBCACHE-1405 URL: https://jira.jboss.org/jira/browse/JBCACHE-1405 Project: JBoss Cache Issue Type: Bug Security Level: Public(Everyone can see) Components: Transactions Affects Versions: 2.1.1.GA Reporter: Krzysztof Sobolewski Assignee: Manik Surtani Fix For: 3.0.0.GA Attachments: CacheTest.java Everything happens in the same transaction. Lets say we have a node /a/b/c. When I remove node /a, all three nodes (up to c) are marked as deleted. When I add node c again under the same path, I get a lock timeout on this node (with not really detailed message). From what I gather, the nodes are marked deleted just fine, but one detail is missing: they are not added as deleted in current transaction (except /a, which I delete explicitly). The removed root is added but its children are not. This causes a failure because PessimisticLockInterceptor.manageReverseRemove() checks whether the node is marked as deleted and whether it is marked as deleted in the current transaction. The latter test fails for /a/b.

Readding a node deleted via a parent node causes lock timeout ------------------------------------------------------------- Key: JBCACHE-1405 URL: https://jira.jboss.org/jira/browse/JBCACHE-1405 Project: JBoss Cache Issue Type: Bug Security Level: Public(Everyone can see) Components: Transactions Affects Versions: 2.1.1.GA Reporter: Krzysztof Sobolewski Assignee: Manik Surtani Attachments: CacheTest.java Everything happens in the same transaction. Lets say we have a node /a/b/c. When I remove node /a, all three nodes (up to c) are marked as deleted. When I add node c again under the same path, I get a lock timeout on this node (with not really detailed message). From what I gather, the nodes are marked deleted just fine, but one detail is missing: they are not added as deleted in current transaction (except /a, which I delete explicitly). The removed root is added but its children are not. This causes a failure because PessimisticLockInterceptor.manageReverseRemove() checks whether the node is marked as deleted and whether it is marked as deleted in the current transaction. The latter test fails for /a/b.