aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions
Date Thu, 14 Dec 2017 11:11:00 GMT

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

David Bosschaert commented on ARIES-1766:
-----------------------------------------

I implemented a fix in: https://svn.apache.org/viewvc?view=revision&revision=1818103

This fix uses an extra service registration property {{warning.exceptions}}. Set the exception
class names on that service registration property that are considered warnings to get them
logged as warning.

> Configure log severity for Whiteboard JMX registration exceptions
> -----------------------------------------------------------------
>
>                 Key: ARIES-1766
>                 URL: https://issues.apache.org/jira/browse/ARIES-1766
>             Project: Aries
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: jmx-1.1.5
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>
> When Aries JMX Whiteboard registers MBeans (in {{org.apache.aries.jmx.whiteboard.MBeanHolder}})
a number of exceptions, including {{InstanceAlreadyExistsException}} are caught and logged
at {{error}} level. 
> Depending on the context these messages may not really be errors, but rather warnings.
It would be good to be able to configure Aries JMX wrt to how these exceptions are logged,
allowing certain ones to appear as warnings in the log instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message