Lorenz Quack created QPID-6516:
----------------------------------
Summary: Tactically switch Broker from Log4j to Logback
Key: QPID-6516
URL: https://issues.apache.org/jira/browse/QPID-6516
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Reporter: Lorenz Quack
As a first step to fully reimplementing logging within the Broker, we first
simply replace Log4J with Logback.
At a high level this change will:
* disable the current management interface at the points where they interact
with the underlying mechanism
* remove all dependencies on Log4J
* *tactically* implement Logback in a manner sufficient to keep the Broker
operational and allow all system tests (apart from those with test logging
management) running.
More detailed: the scope of this change is a follows:
# Make all LoggingManagement Mbean methods throw UnsupportedOperationException
(we will eventually wire this MBean back up the new logging model objects, but
for now it is simplify the change if we disable it)
# Disable tests that test LoggingManagement Mbean
# Disable LogFIleServlet/LogFileListingServlet
# Remove QpidCompositeRollingAppender
# Re-express fallback-log4j.properties, log4jbroker/etc/log4.xml and
test-profiles/test_resources/log4.xml as their functional equivalent in
logback.xml. There is no need to port config for QpidCompositeRollingAppender.
# Re-express log.properties file used by perftests, TCK, interversion as
logback.
# Remove support for the logWatchFrequency and associated command line argument
# Have Broker#main programmatically configure Logback rather than Log4J.
# Where pom.xml files depend on log4j, switch them to logback
# Ensure that perftests, TCK etc are logging correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
