Go to file
Konstantin Lutovich e609b5eeb7 Close consumed inputs in ChunkedWriteHandler (#8876)
Motivation:

ChunkedWriteHandler needs to close both successful and failed
ChunkInputs. It used to never close successful ones.

Modifications:

* ChunkedWriteHandler always closes ChunkInput before completing
the write promise. 
* Ensure only ChunkInput#close() is invoked
on a failed input.
* Ensure no methods are invoked on a closed input.

Result:

Fixes https://github.com/netty/netty/issues/8875.
2019-02-28 21:13:56 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn support publishing snapshots from docker based ci (#8634) 2018-12-07 05:43:06 +01:00
all [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
bom [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
buffer Further reduce ensureAccessible() overhead (#8895) 2019-02-28 20:40:41 +01:00
codec Tighten up contract of PromiseCombiner and so make it more safe to use (#8886) 2019-02-28 20:32:04 +01:00
codec-dns use checkPositive/checkPositiveOrZero (#8835) 2019-02-04 16:01:49 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-http Avoid unnecessary char casts for CookieEncoder (#8827) 2019-02-25 19:50:19 +01:00
codec-http2 Tighten up contract of PromiseCombiner and so make it more safe to use (#8886) 2019-02-28 20:32:04 +01:00
codec-memcache use checkPositive/checkPositiveOrZero (#8835) 2019-02-04 16:01:49 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-stomp use checkPositive/checkPositiveOrZero (#8835) 2019-02-04 16:01:49 +01:00
codec-xml Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
common Tighten up contract of PromiseCombiner and so make it more safe to use (#8886) 2019-02-28 20:32:04 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
docker Update JDK12 and 13 to latest EA releases. (#8809) 2019-02-28 13:54:04 +01:00
example Compare HttpMethod by reference (#8815) 2019-01-30 21:17:00 +01:00
handler Close consumed inputs in ChunkedWriteHandler (#8876) 2019-02-28 21:13:56 +01:00
handler-proxy http-proxy: attach headers to connection exception (#8824) 2019-02-02 07:16:36 +01:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench Further reduce ensureAccessible() overhead (#8895) 2019-02-28 20:40:41 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite DefaultFileRegion.transferTo with invalid count may cause busy-spin (#8885) 2019-02-26 11:08:09 +01:00
testsuite-autobahn Compare HttpMethod by reference (#8815) 2019-01-30 21:17:00 +01:00
testsuite-http2 use checkPositive/checkPositiveOrZero (#8803) 2019-01-31 09:07:14 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport Tighten up contract of PromiseCombiner and so make it more safe to use (#8886) 2019-02-28 20:32:04 +01:00
transport-native-epoll DefaultFileRegion.transferTo with invalid count may cause busy-spin (#8885) 2019-02-26 11:08:09 +01:00
transport-native-kqueue DefaultFileRegion.transferTo with invalid count may cause busy-spin (#8885) 2019-02-26 11:08:09 +01:00
transport-native-unix-common use checkPositive/checkPositiveOrZero (#8803) 2019-01-31 09:07:14 +01:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-sctp use checkPositive/checkPositiveOrZero (#8803) 2019-01-31 09:07:14 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Exclude mainframer related files from git 2018-10-14 13:20:18 +02:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
mvnw Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
mvnw.cmd Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
NOTICE.txt Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
pom.xml Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
README.md Provide an Automatic-Module-Name for the netty-all artifact fixes #7644 2018-01-27 20:31:16 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.