[
https://issues.apache.org/jira/browse/SLING-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424060#comment-15424060
]
Konrad Windszus commented on SLING-5888:
----------------------------------------
The logic of the attached patch is as follows:
# It lists all the processed resources of the OSGi installer.
# If the resource's location starts with one of the given prefixes (only
{{jcrinstall:/apps}}) by default it will check if the given resource was
successfully installed.
# If that is not the case and there is no other resource matching the prefix in
the same resource group which was successfully installed it makes the health
check emit a warning.
As far as I understood the healthcheck will only fail in case
# there is another bundle with the same symbolic name provided by some other
provider (not the JCR Installer from /apps) with higher priority or with a
newer version. This is also triggered in case the bundle was uploaded manually
through the web console.
# there is another configuration with the same PID provided by some other
provider (not the JCR Installer from /apps) with higher priority. This is also
triggered in case the configuration was manually overwritten in the Felix Web
Console.
> Health Check for detecting not-installed configurations/bundles from the OSGi
> installer
> ---------------------------------------------------------------------------------------
>
> Key: SLING-5888
> URL: https://issues.apache.org/jira/browse/SLING-5888
> Project: Sling
> Issue Type: Improvement
> Components: Health Check, Installer
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Attachments: SLING-5888-v01.patch
>
>
> We faced an issue in the past that configurations (or bundles) being deployed
> in the repository are not effective (i.e. not installed in Apache Felix).
> The reason for that is that the OSGi configuration was either manually
> modified in the Web Console (and therefore takes precedence over the version
> of the configuration being deployed in the repository) or in case of bundles,
> that the same bundle has already been deployed in that or a newer version
> (manually or through some other path in the repository/filesystem).
> Both states may lead to issues at run time, so it would be good to have an
> automated check for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
