You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/08/12 14:27:46 UTC
[jira] [Resolved] (QPID-6689) [Java Broker] QpidTurboFilter
prevents any log messages from being logged until NameAndLevelFilters are
activated
[ https://issues.apache.org/jira/browse/QPID-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-6689.
------------------------------
Resolution: Fixed
This implementation will work for the initial startup of the Broker within the JVM, but for situations where the Broker is restarted (such as the system tests), log messages are still going to be lost (until the Broker configured at least one filter). Perhaps changing the turbo filter so that is allows in the case where there are no filters would be better.
> [Java Broker] QpidTurboFilter prevents any log messages from being logged until NameAndLevelFilters are activated
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6689
> URL: https://issues.apache.org/jira/browse/QPID-6689
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Alex Rudyy
> Assignee: Keith Wall
> Priority: Blocker
> Fix For: qpid-java-6.0
>
>
> logback invokes TurboFilters before ordinary Filters to decide whether log event should be logged. If TurboFilter denies the event, the log event is not appended.
> Qpid registers QpidTurboFilter which uses log levels set on ordinary Filters to decide whether event should be logged or not. If no ordinary filter is available for the logger, log level OFF is used and any log event issued before registering ordinary Filters is ignored.
> In Qpid broker ordinary Filters are registered on activating of NameAndLevelFilters. Thus, any log event created on Broker startup from resolution phase of BrokerLogger to attaining the state by the NameAndLevelFilters are ignored. As result, any resolution, validation or opening exception thrown before attaining the state by the NameAndLevelFilters is not logged making it difficult to analyze and investigate the problems caused by misconfiguration.
--
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