[
https://issues.apache.org/jira/browse/SLING-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137421#comment-14137421
]
Carsten Ziegeler commented on SLING-3920:
-----------------------------------------
While I'm not against changing the log level, this message only appears if the
topology is changing (new instance, instance stops etc.) Does this happen so
frequent in your system?
> Topology messages fill logs.
> ----------------------------
>
> Key: SLING-3920
> URL: https://issues.apache.org/jira/browse/SLING-3920
> Project: Sling
> Issue Type: Bug
> Reporter: Ian Boston
> Assignee: Ian Boston
>
> In a medium size installations with numerous JobQueues the following topology
> messages fill the logs, making it harder to analyse other messages. Because
> they share the same loggers as Job Management it is not possible to turn down
> the noise levels and exclude the messages without loosing other information
> vital to analysis. Unless there is a strong reason to the contrary, the
> messages should be at DEBUG level.
> {code}
> org.apache.sling.event.impl.jobs.JobConsumerManager Updating property
> provider with ....
> org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event
> TopologyEvent ....
> {code}
> There may be other similar messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
