Stefan Egli created SLING-6178:
----------------------------------

             Summary: quartz-scheduler: lower log.error to debug and move 
information to webconsole
                 Key: SLING-6178
                 URL: https://issues.apache.org/jira/browse/SLING-6178
             Project: Sling
          Issue Type: Improvement
          Components: Commons
    Affects Versions: Commons Scheduler 2.5.0
            Reporter: Stefan Egli
            Assignee: Stefan Egli
            Priority: Minor
             Fix For: Commons Scheduler 2.5.2


[Here|https://github.com/apache/sling/blob/d5112dac6832d6fc3260159ee6e3cd3f31f371a7/bundles/commons/scheduler/src/main/java/org/apache/sling/commons/scheduler/impl/QuartzJobExecutor.java#L78]
 a log.error is issued when the scheduler would like to start a job that is 
dependent on discovery. At startup and during bundle redeployment it is a legal 
situation that scheduler is up and discovery not (yet). Therefore it seems too 
loud to issue a log error.

Thus lowering this to debug and instead providing this info in the webconsole 
under status-slingscheduler instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to