qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6708) Changing LoggingLevel on an existing filter does not always take immediate effect
Date Mon, 31 Aug 2015 15:40:46 GMT

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

Keith Wall updated QPID-6708:
-----------------------------
    Affects Version/s: qpid-java-6.0

> 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
>    Affects Versions: qpid-java-6.0
>            Reporter: Keith Wall
>            Priority: Minor
>             Fix For: qpid-java-6.0
>
>
> 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


Mime
View raw message