Go to file
Norman Maurer ea8ff3b4f6 Not use safeRelease(...) but release(...) to release non-readable holders to ensure we not mask errors.
Motivation:

AbstractChannel attempts to "filter" messages which are written [1]. A goal of this process is to copy from heap to direct if necessary. However implementations of this method [2][3] may translate a buffer with 0 readable bytes to EMPTY_BUFFER. This may mask a user error where an empty buffer is written but already released.

Modifications:

Replace safeRelease(...) with release(...) to ensure we propagate reference count issues.

Result:

Fixes [#7383]
2017-12-04 20:39:19 +01: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-11-09 00:08:30 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
buffer Dont use ThreadDeathWatcher to cleanup PoolThreadCache if FastThreadLocalThread with wrapped Runnable is used 2017-11-28 13:43:49 +01:00
codec [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
codec-http Add tests for HttpObjectDecoder related to limits 2017-11-28 13:41:24 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
common Dont use ThreadDeathWatcher to cleanup PoolThreadCache if FastThreadLocalThread with wrapped Runnable is used 2017-11-28 13:43:49 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
handler Fixed default OpenSsl cipher suites 2017-11-29 12:23:35 +01: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-11-09 00:08:30 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
testsuite-osgi Provide a test for #6548 using the OSGi test suite 2017-11-27 19:52:49 +01:00
transport Improved error message in FixedChannelPool 2017-11-13 20:29:21 +01:00
transport-native-epoll Not use safeRelease(...) but release(...) to release non-readable holders to ensure we not mask errors. 2017-12-04 20:39:19 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00: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 [maven-release-plugin] prepare for next development iteration 2017-11-09 00:08:30 +00: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

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.