You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2017/05/05 13:10:04 UTC
[jira] [Closed] (SLING-6020) Reduce log error 'No Descriptor value
available' down to warn
[ https://issues.apache.org/jira/browse/SLING-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli closed SLING-6020.
------------------------------
> Reduce log error 'No Descriptor value available' down to warn
> -------------------------------------------------------------
>
> Key: SLING-6020
> URL: https://issues.apache.org/jira/browse/SLING-6020
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Oak 1.2.8
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Minor
> Fix For: Discovery Oak 1.2.10
>
>
> During OSGi service re-registration it can happen that the following exception occurrs:
> {noformat}java.lang.Exception: No Descriptor value available
> at org.apache.sling.discovery.commons.providers.spi.base.DiscoveryLiteDescriptor.getDescriptorFrom(DiscoveryLiteDescriptor.java:45)
> at org.apache.sling.discovery.oak.cluster.OakClusterViewService.getLocalClusterView(OakClusterViewService.java:111)
> at org.apache.sling.discovery.base.commons.BaseDiscoveryService.getTopology(BaseDiscoveryService.java:77)
> at org.apache.sling.discovery.oak.OakDiscoveryService.checkForTopologyChange(OakDiscoveryService.java:657)
> at org.apache.sling.discovery.oak.pinger.OakViewChecker.discoveryLiteCheck(OakViewChecker.java:232)
> at org.apache.sling.discovery.oak.pinger.OakViewChecker.access$000(OakViewChecker.java:64)
> at org.apache.sling.discovery.oak.pinger.OakViewChecker$1.run(OakViewChecker.java:208)
> at org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.safelyRun(PeriodicBackgroundJob.java:86)
> at org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.run(PeriodicBackgroundJob.java:77)
> at java.lang.Thread.run(Unknown Source){noformat}
> {noformat}
> In this case a log ERROR is perhaps a bit loud.
> Reduce that to log WARN (without the exception)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)