[QPID-6569] Begin capturing logback logging events at startup and replay those events once the BrokerLoggers are ready

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-6.0
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 04/Jun/15 09:08
• Updated: 28/Sep/15 22:54
• Resolved: 28/Sep/15 22:54

Description

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.