You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2020/02/06 10:08:00 UTC
[jira] [Updated] (SLING-8764) A metric named
commons.scheduler.oldest.running.job.millis already exists
[ https://issues.apache.org/jira/browse/SLING-8764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A. J. David Bosschaert updated SLING-8764:
------------------------------------------
Fix Version/s: Commons Scheduler 2.7.6
> A metric named commons.scheduler.oldest.running.job.millis already exists
> -------------------------------------------------------------------------
>
> Key: SLING-8764
> URL: https://issues.apache.org/jira/browse/SLING-8764
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Reporter: Miroslav Beranič
> Assignee: Stefan Egli
> Priority: Minor
> Fix For: Commons Scheduler 2.7.6
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> GaugesSupport throws an exception when activation happens after first time, as metrics do not get unregistered from the MetricRegistry.
> Method @Deactivate should be updated to unregister registered metric at the @Activate method.
> There seems to be already some-kind of metric-name tracking, but do not know what is the useage. So I've created "quick&easy" solution, to track registered metric names and use this name array at the @Deactivate to unregister metric names.
>
> I will provide PR at the project GitHub page located at the:
> https://github.com/apache/sling-org-apache-sling-commons-scheduler
>
> This is just a proposal, I guess author knows what is missing better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)