Go to file
Scott Mitchell cafce0e71a SingleThreadEventLoopTest failures
Motivation:
Some unit tests in SingleThreadEventLoopTest rely upon Thread.sleep for sequencing events between threads. This can be unreliable and result in spurious test failures if thread scheduling does not occur in a fair predictable manner.

Modifications:
- Reduce the reliance on Thread.sleep in SingleThreadEventLoopTest

Result:
Fixes https://github.com/netty/netty/issues/5851
2016-10-11 09:10:25 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +02:00
buffer [#5833] Ensure direct memory is released when DirectPoolArena is collected 2016-09-23 15:21:14 -07:00
codec Fix typo in ProtobufDecoder comment 2016-10-10 07:40:52 +02:00
codec-haproxy This PR fixes an issue with the PROXY protocol where the reader index of a consumed byte array was not set correctly. 2016-09-29 21:21:18 +02:00
codec-http HttpObjectDecoder resetRequested not updated after reset 2016-09-22 13:46:02 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +02:00
common Pre-increment leakCheckCnt to prevent false leak-detectation for very first time 2016-09-29 14:14:13 +02:00
example Remove OSGi import of JCTools since it is shaded. 2016-09-13 14:22:29 -07:00
handler [#5860] Ensure removal of SslHandler not produce IllegalReferenceCountException 2016-10-10 11:06:32 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Upgrade JMH to 1.14.1 2016-09-29 21:31:27 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +02:00
testsuite Fix compilation failure introduced by 366130c6b3 2016-09-22 08:44:28 -07:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +02:00
transport SingleThreadEventLoopTest failures 2016-10-11 09:10:25 +02:00
transport-native-epoll [#5882] Ensure we even process tasks if processing of ready channels throws an Exception in event loop. 2016-10-10 07:50:09 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +02:00
transport-sctp Improve SctpMessageCompletionHandler 2016-09-19 16:00:14 -07:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-08-26 08:36:54 +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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Update AlpnAgent version 2016-10-10 18:51:34 -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 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.