0dacd52007
Motivation: InternalLoggerFactory either sets a default logger factory implementation based on the logging implementations on the classpath, or applications can set a logger factory explicitly. If applications wait too long to set the logger factory, Netty will have already set a logger factory leading to some objects using one logging implementation and other objets using another logging implementation. This can happen too if the application tries to set the logger factory twice, which is likely a bug in the application. Yet, the Javadocs for InternalLoggerFactory warn against this saying that InternalLoggerFactory#setLoggerFactory "should be called as early as possible and shouldn't be called more than once". Instead, Netty should guard against this. Modications: We replace the logger factory field with an atomic reference on which we can do CAS operations to safely guard against it being set twice. We also add an internal holder class that captures the static interface of InternalLoggerFactory that can aid in testing. Result: The logging factory can not be set twice, and applications that want to set the logging factory must do it before any Netty classes are initialized (or the default logger factory will be set).
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.