Go to file
Scott Mitchell cc8140b41c HTTP/2 unit test failure race condition
Motivation:
HttpToHttp2ConnectionHandler is awaiting on a future and a latch that may be competed before the buffers actually get released.  This test is attempting to validate that the buffer's refCnt() is 0 but there is no mechanism to wait on for a buffer's release() method to be called.

Modifications:
Remove the buffer refCnt() check.  The leak profile is designed to pick these up.

Result:
Unit tests that no longer have a race condition.
2014-12-12 14:44:38 -05:00
all Fix missing version properties of transport-epoll in all-in-one JAR 2014-10-21 22:36:19 +09:00
buffer Ensure buffer is not released when call array() / memoryAddress() 2014-12-11 11:31:05 +01:00
codec Headers set/add/contains timeMillis methods 2014-12-06 22:40:45 +09:00
codec-dns Add EDNS support to DnsQueryEncoder 2014-10-16 17:06:20 +09:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:08 +02:00
codec-http Fix AbstractDiskHttpData int conversion from long 2014-12-08 07:18:09 +01:00
codec-http2 HTTP/2 unit test failure race condition 2014-12-12 14:44:38 -05:00
codec-memcache Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-mqtt Fix dependency issues with hamcrest 2014-12-04 17:53:35 +09:00
codec-socks Add proxy support for client socket connections 2014-10-14 12:40:33 +09:00
codec-stomp Headers set/add/contains timeMillis methods 2014-12-06 22:40:45 +09:00
common Fixing minor typo in FastThreadLocal javadoc. 2014-12-08 14:24:07 +01:00
example Refactoring HTTP/2 Flow Control interfaces. 2014-12-08 09:16:06 -08:00
handler Make sure to notify handshake success even if SSLEngine is closed 2014-12-12 11:55:34 +09:00
handler-proxy Use Proxy-Authorization instead of Authorization for proxy authentication 2014-11-20 20:39:18 +09:00
license Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
microbench Benchmark for HttpRequestDecoder 2014-11-12 14:20:38 +01:00
resolver Fix memory leak in NameResolverGroup 2014-11-20 20:22:17 +09:00
resolver-dns Fix Java 6 compatibility issue in DnsNameResolver 2014-12-06 22:33:45 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Add more assertions related with TLS renegotiation 2014-12-12 18:01:36 +09:00
transport Fix documentation for ChannelHandlerContext#fireChannelReadComplete 2014-12-12 18:34:40 +01:00
transport-native-epoll Remove bottleneck while create InetSocketAddress in native transport 2014-12-12 18:23:18 +01:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Allow to obtain RecvByteBufAllocator.Handle to allow more flexible implementations 2014-08-12 06:54:29 +02:00
transport-udt Small performance improvements 2014-11-19 23:44:25 -05:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implemented LZMA frame encoder 2014-09-15 15:14:15 +02:00
pom.xml HTTP/2 Draft 16 2014-12-11 18:58:59 -05:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:49:27 +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 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.