[
https://issues.apache.org/jira/browse/QPID-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-2012:
---------------------------------
Fix Version/s: 0.6
> Logging Design does not take into consideration logging before broker
> configuration has been processed
> ------------------------------------------------------------------------------------------------------
>
> Key: QPID-2012
> URL: https://issues.apache.org/jira/browse/QPID-2012
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Marnie McCormack
> Fix For: 0.6
>
>
> The current Technical Design only describes changes to be completed to use
> log4j for logging and to log based on the configuration setup.
> The majority of the Broker Startup messages in the specification are logged
> before the configuration has been loaded.
> The design also does not include a LogSubject against which Broker level
> messages should be logged, nor is there a LogActor to log messages during
> startup/shutdown. Although if shutdown could be requested via the
> ManagementConsole concievably that would be the current actor.
> One approach would be to:
> - create a SystemOutRootLogger that is always enabled and used until the
> configuration has been read.
> - create a BrokerLogSubject that would not add anything additional to the log
> format.
> - create a BrokerLogActor that is set during startup and broker initiated
> shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
