Go to file
Norman Maurer b9101b0331 [#2823] Writing DefaultFileRegion with EpollSocketChannel may cause hang
Motivation:

In EpollSocketchannel.doWriteFileRegion(...) we need to make sure we write until sendFile(...) returns either 0 or all is written. Otherwise we may not get notified once the Channel is writable again.

This is the case as we use EPOLL_ET.

Modifications:

Always write until either sendFile returns 0 or all is written.

Result:

No more hangs when writing DefaultFileRegion can happen.
2014-08-26 15:07:02 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
codec Check noJdkZlibEncoder before comparing other parameters 2014-08-26 16:11:45 +09:00
codec-http Reduce memory copies in spdy compression implementation. 2014-08-21 11:26:13 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
common Avoid redundant reads of head in peakNode 2014-08-21 08:44:17 +02:00
example Fix example for Http Upload 2014-08-18 10:49:05 +02:00
handler [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
testsuite Better fix for TrafficShapingHandlerTest 2014-08-16 18:11:36 +02:00
transport [#2586] Use correct EventExecutor to notify for bind failures on late registration 2014-08-20 16:32:39 +02:00
transport-native-epoll [#2823] Writing DefaultFileRegion with EpollSocketChannel may cause hang 2014-08-26 15:07:02 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09: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 license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-08-16 03:02:02 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +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

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.