Go to file
Scott Mitchell a7007cab51 Deprecate and ignore ResourceLeakDetector's maxActive parameter
Motivation:
ResourceLeakDetector supports a parameter called maxActive. This parameter is used in attempt to limit the amount of objects which are being tracked for leaks at any given time, and generates an error log message if this limit is exceeded. This assumes that there is a relationship between leak sample rate and object lifetime for objects which are already being tracked. This relationship may appear to work in cases were there are a single leak record per object and those leak records live for the lifetime of the application but in general this relationship doesn't exist. The original motivation was to provide a limit for cases such as HashedWheelTimer to limit the number of instances which exist at any given time. This limit is not enforced in all circumstances in HashedWheelTimer (e.g. if the thread is a daemon) and can be implemented outside ResourceLeakDetector.

Modifications:
- Deprecate all methods which interact with maxActive in ResourceLeakDetectorFactory and ResourceLeakDetector
- Remove all logic related to maxActive in ResourceLeakDetector
- HashedWheelTimer implements its own logic to impose a limit and warn users if too many instances exists at any given time.

Result:
Fixes https://github.com/netty/netty/issues/6225.
2017-02-08 20:00:14 -08:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
buffer Only use Mockito for mocking. 2017-02-07 08:56:36 +01:00
codec Simplification of boolean expression 2017-02-07 14:35:38 -08:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
codec-http Only use Mockito for mocking. 2017-02-07 08:56:36 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
common Deprecate and ignore ResourceLeakDetector's maxActive parameter 2017-02-08 20:00:14 -08:00
example [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
handler SslHandler avoid calling wrap/unwrap when unnecessary 2017-02-07 00:12:53 -08:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Allow to allign allocated Buffers 2017-02-06 09:51:06 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
testsuite Only use Mockito for mocking. 2017-02-07 08:56:36 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport Only use Mockito for mocking. 2017-02-07 08:56:36 +01:00
transport-native-epoll Cleanup : for loops for arrays to make code easier to read and removed unnecessary toLowerCase() 2017-02-06 07:48:34 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Only use Mockito for mocking. 2017-02-07 08:56:36 +01:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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:

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.