[QPID-6516] Tactically switch Broker from Log4j to Logback

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: qpid-java-6.0
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Lorenz Quack
• Created: 29/Apr/15 09:00
• Updated: 06/May/15 21:02
• Resolved: 06/May/15 21:02

Description

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:

1. 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)
2. Disable tests that test LoggingManagement Mbean
3. Disable LogFIleServlet/LogFileListingServlet
4. Remove QpidCompositeRollingAppender
5. 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.
6. Re-express log.properties file used by perftests, TCK, interversion as logback.
7. Remove support for the logWatchFrequency and associated command line argument
8. Have Broker#main programmatically configure Logback rather than Log4J.
9. Where pom.xml files depend on log4j, switch them to logback
10. Ensure that perftests, TCK etc are logging correctly.