[
https://issues.apache.org/jira/browse/QPID-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572929#comment-14572929
]
ASF subversion and git services commented on QPID-6569:
-------------------------------------------------------
Commit 1683568 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1683568 ]
QPID-6569: [Java Broker] Begin capturing logback logging events at startup and
replay those events once the BrokerLoggers are ready (work done by Lorenz Quack
and Alex Rudyy)
> 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: Improvement
> 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.
> If there is no Broker logging configured in the Broker model, or there is
> Broker logging but Logback fails, the Broker must fail to startup. Any log
> events captured should be written to stdout to allow the user to diagnose
> the problem. By default a LogLevel filter of INFO should be applied, but this
> should be overridable with a system property so that all messages can be
> seen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
