aries-dev mailing list archives

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

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

ASF subversion and git services commented on ARIES-1766:
--------------------------------------------------------

Commit 1818103 from [~bosschaert] in branch 'aries/trunk'
[ https://svn.apache.org/r1818103 ]

ARIES-1766 Configure log severity for Whiteboard JMX registration exceptions

The severity can be configured by specifying one or more classes with the 
  warning.exceptions
service property of the whiteboard service. Any exceptions listed there are logged 
as warnings, other ones are logged as errors.

> 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