Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
If a provider is reporting new artifacts and these artifacts need to be copied into the local storage (like JCR artifacts), there is a slight change that while the OSGi installer is processing the new artifacts, the same provider is updating the artifacts which then results in a null stored in the internal data objects for the file, although it is still available. The artifact can't be installed anymore as the file is not available.
This is due to the logic in FileDataStore#createNewDataFile which returns null if the file is already cached.