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 2014/11/04 14:44:34 UTC

[jira] [Commented] (SLING-3920) Topology messages fill logs.

    [ https://issues.apache.org/jira/browse/SLING-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196103#comment-14196103 ] 

Stefan Egli commented on SLING-3920:
------------------------------------

[~ianeboston], [~cziegeler], (how) should we proceed on this one?

> Topology messages fill logs.
> ----------------------------
>
>                 Key: SLING-3920
>                 URL: https://issues.apache.org/jira/browse/SLING-3920
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Event 3.4.2
>            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)