You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/08/23 19:34:45 UTC
[jira] [Commented] (QPID-6708) Changing LoggingLevel on an existing
filter does not always take immediate effect
[ https://issues.apache.org/jira/browse/QPID-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708451#comment-14708451 ]
ASF subversion and git services commented on QPID-6708:
-------------------------------------------------------
Commit 1697229 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1697229 ]
QPID-6708: [Java Broker] Make a change in level on an existing LevelFilter notify the turbo filter so it may invalidate its cache
> Changing LoggingLevel on an existing filter does not always take immediate effect
> ---------------------------------------------------------------------------------
>
> Key: QPID-6708
> URL: https://issues.apache.org/jira/browse/QPID-6708
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Priority: Minor
>
> In the default configuration there is no DEBUG filter.
> If one changes an existing INFO filter (e.g., the "Qpid" filter) to DEBUG the debug messages do not show up in the logs.
> The suspicion is that the TurboFilter is not being properly updated when an existing filter changes level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org