Go to file
Norman Maurer 534de73d28
Workaround JDK bug that will cause an AssertionError when calling ServerSocketChannel.config().getOptions(). (#8183)
Motivation:

There is a JDK bug which will return IP_TOS as supported option for ServerSocketChannel even if its not supported afterwards and cause an AssertionError.
See http://mail.openjdk.java.net/pipermail/nio-dev/2018-August/005365.html.

Modifications:

Add a workaround for the JDK bug.

Result:

ServerSocketChannel.config().getOptions() will not throw anymore and work as expected.
2018-08-09 13:11:08 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn/wrapper Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
all [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
buffer CompositeByteBuf nioBuffer doesn't always alloc (#8176) 2018-08-07 11:31:24 +02:00
codec [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
common [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
docker Update to java 11+ea19 2018-06-25 16:47:01 +02:00
example [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
handler Fix NPE exception when using invalid cipher during building SslContext. (#8171) 2018-08-02 21:42:21 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
resolver-dns DnsNameResolver hangs if search domain results in invalid hostname (#8180) 2018-08-08 08:14:18 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
testsuite Adjust SSL related tests to be more correct and so pass in the next EA release of java11. (#8162) 2018-08-01 06:37:53 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
testsuite-shading Disable test as it sometimes fails on the CI 2018-08-01 08:31:31 +02:00
transport Workaround JDK bug that will cause an AssertionError when calling ServerSocketChannel.config().getOptions(). (#8183) 2018-08-09 13:11:08 +02:00
transport-native-epoll Lazy initialize NativeDatagramPacketArray and IovArray in EpollEventLoop (#8160) 2018-07-29 18:22:27 +08:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-07-27 04:59:28 +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 Add docker-sync files to .gitignore 2018-05-15 10:39:14 +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 Workaround JDK bug that will cause an AssertionError when calling ServerSocketChannel.config().getOptions(). (#8183) 2018-08-09 13:11:08 +02: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.