You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2020/09/14 14:40:00 UTC

[jira] [Assigned] (FELIX-4678) No list of blacklisted services available

     [ https://issues.apache.org/jira/browse/FELIX-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reassigned FELIX-4678:
---------------------------------------

    Assignee: Carsten Ziegeler  (was: Jean-Baptiste Onofré)

> No list of blacklisted services available
> -----------------------------------------
>
>                 Key: FELIX-4678
>                 URL: https://issues.apache.org/jira/browse/FELIX-4678
>             Project: Felix
>          Issue Type: Improvement
>          Components: Event Admin
>    Affects Versions: eventadmin-1.4.2
>            Reporter: Jörg Hoh
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: eventadmin-1.5.2
>
>
> When a service gets blacklisted by the eventAdmin, there is only a single warn statement in the logs. It would be great, if it would be an error, as a blacklisted service normally results in application problems. And if it's printed as error, it should be catched by any log analyzing mechanism.
> On top it would be good, if blacklisted services can be detected by a different way (e.g. by throwing an OSGI event, updating an JMX MBean or something like that). Log parsing is cumbersome if you need to do online monitoring of your application.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)