[
https://issues.apache.org/jira/browse/SLING-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-7370:
----------------------------------
Description:
While using the file system resource provider in a development scenario, with
sample content in JSON format, it turned out that the resource provider never
recovered from a syntax error in a JSON file, even after the error was fixed.
Only after restarting the bundle the resource was ok again. The same behaviour
was then also verified with the FileVault XML format.
The scenario was observed on a Sling system with multiple listeners for
resource change events, which access the changed resource right after the
change. It seems that there is a race in the way {{FileMonitor}} updates the
{{ContentFileCache}} ans sends events.
Sending the events after removing the cache-entry seems to fix the problem.
was:
While using the file system resource provider in a development scenario, with
sample content in JSON format, it turned out that the resource provider never
recovered from a syntax error in a JSON file, even after the error was fixed.
Only after restarting the bundle the resource was ok again.
The scenario was observed on a Sling system with multiple listeners for
resource change events, which access the changed resource right after the
change. It seems that there is a race in the way {{FileMonitor}} updates the
{{ContentFileCache}} ans sends events.
Sending the events after removing the cache-entry seems to fix the problem.
> File system resource provider may never recover from JSON/XML syntax errors
> ---------------------------------------------------------------------------
>
> Key: SLING-7370
> URL: https://issues.apache.org/jira/browse/SLING-7370
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: File System Resource Provider 2.1.8
> Reporter: Julian Sedding
> Priority: Minor
> Fix For: File System Resource Provider 2.1.10
>
> Attachments: SLING-7370.patch
>
>
> While using the file system resource provider in a development scenario, with
> sample content in JSON format, it turned out that the resource provider never
> recovered from a syntax error in a JSON file, even after the error was fixed.
> Only after restarting the bundle the resource was ok again. The same
> behaviour was then also verified with the FileVault XML format.
> The scenario was observed on a Sling system with multiple listeners for
> resource change events, which access the changed resource right after the
> change. It seems that there is a race in the way {{FileMonitor}} updates the
> {{ContentFileCache}} ans sends events.
> Sending the events after removing the cache-entry seems to fix the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
