-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 6.0-HF27, 7.10-HF06, 8.1
-
Component/s: Nuxeo Drive
In the following scenario: 2 Drive clients are connected to different server nodes are accessing the same document.
The document is moved by one of the 2 clients , if the GetChangeSummary for the second one arrives on the server before the cluster invalidation delay. the old title is returned to this client as the .'fileSystemItemName' .
This happens for the following reason:
- in ES the event is registered correctly
- the documentMoved is picked up by the AuditChangeFinder
- the fileSystem properties (including the fileSystemItemName) returned to the client are actually initialized from the document model ex in DocumentBackedFolderItem ( see initialize method), so if the thread returning the documentMoved event doesn't have the updated doc model it will return it to the client with the wrong title ( New Folder);
Example:
In ES:
"audit","entry","2091501","13.413756","logEntry","eventDocumentCategory","41","project","/7f95b97f-8978-4d92-8500-f81fd3163609/UserWorkspaces/41/ABC","Folder","a590937d-d30a-4448-aaee-44973fe2ca13","documentMoved","default","2016-02-18T07:21:06.398Z","2091501","2016-02-18T07:21:06.494Z",,,"default:34310c17-f584-4c68-b72f-7fb6d2f99b1a","7f95b97f-8978-4d92-8500-f81fd3163609","ABC","ABC","/7f95b97f-8978-4d92-8500-f81fd3163609/UserWorkspaces/41"
But Drive gets:
{"eventId":"documentMoved","eventDate":1455780066398,"repositoryId":"default","fileSystemItem":
,"docUuid":"a590937d-d30a-4448-aaee-44973fe2ca13","fileSystemItemId":"defaultFileSystemItemFactory#default#a590937d-d30a-4448-aaee-44973fe2ca13","fileSystemItemName":"New folder"},
- is related to
-
NXP-22284 Fix random failure on AuditChangeFinderClusteringEnabledTestSuite with ES
- Resolved