You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/03/07 19:10:40 UTC
[jira] [Created] (SLING-5591) Race condition in installer: cached
artifacts might be made unavailable
Carsten Ziegeler created SLING-5591:
---------------------------------------
Summary: Race condition in installer: cached artifacts might be made unavailable
Key: SLING-5591
URL: https://issues.apache.org/jira/browse/SLING-5591
Project: Sling
Issue Type: Bug
Components: Installer
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Installer Core 3.6.8
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)