andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
7,411 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
e8e317bdb3
Go to file
louxiu e8e317bdb3 Calculate correct lastRecords size 
Motivation:
ResourceLeakDetector records at most MAX_RECORDS+1 records

Modifications:
Make room before add to lastRecords

Result:
ResourceLeakDetector will record at most MAX_RECORDS records
2017-07-18 19:14:50 -07: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-07-06 07:37:47 +02:00
bom [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
buffer Record release when enable detailed leak detection 2017-07-18 09:32:23 +02:00
codec [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
codec-http Only add / to uri if really needed. 2017-07-18 09:27:20 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
common Calculate correct lastRecords size 2017-07-18 19:14:50 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
handler SSLEngineTest should not depend on OpenSsl* class. 2017-07-18 13:24:22 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
testsuite Explicit specify hostaddress during tests to ensure testsuite pass on docker (mac) 2017-07-18 07:24:24 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
transport Add testcase to ensure NioEventLoop.rebuildSelector() works correctly. 2017-07-18 07:20:31 +02:00
transport-native-epoll Explicit specify hostaddress during tests to ensure testsuite pass on docker (mac) 2017-07-18 07:24:24 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-07-06 07:37:47 +02: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 Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml Use unbounded queues from JCTools 2.0.2 2017-07-10 12:36:12 -07: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 UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02:00

README.md

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:

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.