cancel
Showing results for 
Search instead for 
Did you mean: 

Uploading multiple files - randomly throws 'Node does not exist' exception

eu_81
Champ in-the-making
Champ in-the-making
Hello,

I have an issue with uploading multiple files using Alfresco Share (Alfresco Enterprise 3.4.9, Windows 7 Enterprise) regarding the inexistence of the node in repository which its content I'm uploading.
The contents of the uploaded files are stored in a "customized" content store (extends org.alfresco.repo.content.AbstractContentStore). The "customized" content store is in fact an interface to a WORM (Write-Once-Read-Many) Storage System and it use the HTTP/S to communicate with it.

The problem appears randomly, only when I'm uploading a large number of files (about ~457 - each file having ~3 MB size). The location where the error occurs is on the "content stream closing" method (implementation of org.alfresco.service.cmr.repository.ContentStreamListener.contentStreamClosed). In this method, I have to do some extra operations to the newly uploaded content to the "WORM" storage, such as: adding some custom-metadata, set content retention etc. The data are retrieved from the node properties.
The odd thing is, even the Share tells me that the document has failed to upload, the content and its "WORM" metadata are set OK and I can access it from Share/Explore without any problem - I belive there is a retrying sequence in case of errors … (I noticed in the log file that the "content stream closing" method is called twice ..).

So, what can be the reason of this behavior?

The complete scenario of uploading files is bellow:
1. Create a space having associated a content rule that executes a web script.
The web scripts set some metadata to a custom aspect of ours and attaches it to the current document (node). The custom aspect triggers further the attachment of the "cm:storeSelector" aspect having a specific store name set …
2. Start upload the multiple files to the above space …

Attached are the alfresco log file and the web script.

Best regards,
Emil
1 REPLY 1

mrogers
Star Contributor
Star Contributor
Sounds like a concurrency bug.  Or incorrect rollback handling.   Have you tried calling Alfresco Support?   On one hand they may not be able to help if the bug is due to your custom code,  however I've got a dim memory that there have been a few of these sort of bugs fixed.