You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2015/06/04 11:17:38 UTC
[jira] [Updated] (QPID-6569) Begin capturing logback logging events
at startup and replay those events once the BrokerLoggers are ready
[ https://issues.apache.org/jira/browse/QPID-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-6569:
-----------------------------
Attachment: QPID-6569-Collect-all-start-up-logs-before-and-reply-after-logs-are-configured.diff
> Begin capturing logback logging events at startup and replay those events once the BrokerLoggers are ready
> ----------------------------------------------------------------------------------------------------------
>
> Key: QPID-6569
> URL: https://issues.apache.org/jira/browse/QPID-6569
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 6.0 [Java]
> Reporter: Alex Rudyy
> Fix For: 6.0 [Java]
>
> Attachments: QPID-6569-Collect-all-start-up-logs-before-and-reply-after-logs-are-configured.diff
>
>
> With the current implementation, log events generated by Qpid and dependencies between Broker startup and the point in time when the BrokerLoggers are recovered/opened are lost.
> Change the implementation so that logback logging events are captured and then replayed once the Logging model objects are ready.
--
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