Attached is a test case that shows that using workspace move concurrent with other write operations causes inconsistencies.
The problem is that unlike session move, workspace move operates on the local item state directly (session move operates on transient item state). When a concurrent modification occurs on for instance the source parent of the moved target the modification that the move operation was trying to do is overwritten as the changes from the concurrent session are pulled in:
- on thread 1 a workspace.move is initiated on /folder1/node to /folder2/node, removing the child node entry from /folder1 a.o.t.
- session 2 on thread 2 modifies and saves /folder1, overwriting the changes on the local item state of /folder1 in session 1
- thread 1, still in the workspace move operation, sends the updates to the shared item state manager