[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1067) Concurrent node removal detection is not working correctly in OptimisticValidatorInterceptor.java

[ http://jira.jboss.com/jira/browse/JBCACHE-1067?page=comments#action_12369382 ] Javier Pedrido commented on JBCACHE-1067: ----------------------------------------- Manik, I'm not talking about concurrent node creation (JBCACHE-1026). The bug is about concurrent node deletion (a different validation). I'm proposing to change (HEAD): // if this is a newly created node then we expect the underlying node to be null. // if not, we have a problem... if (underlyingNode == null && !workspaceNode.isCreated() ) { throw new DataVersioningException("Underlying node for " + fqn + " is null, and this node wasn't newly created in this transaction! We have a concurrent deletion event."); } To: // if this is a newly created node then we expect the underlying node to be null. // if not, we have a problem... if (underlyingNode == null && !workspaceNode.isCreated() && workspaceNode.isDirty()) { throw new DataVersioningException("Underlying node for " + fqn + " is null, and this node wasn't newly created in this transaction! We have a concurrent deletion event."); } -- 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