qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6569) Begin capturing logback logging events at startup and replay those events once the BrokerLoggers are ready
Date Thu, 04 Jun 2015 13:57:38 GMT

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

Alex Rudyy updated QPID-6569:
-----------------------------
    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. 

  was:
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. 


> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message