Go to file
Julien Viet e348bd9217 KQueueEventLoop | EpollEventLoop may incorrectly update registration when FD is reused.
Motivation:

The current KQueueEventLoop implementation does not process concurrent domain socket channel registration/unregistration in the order they actual
happen since unregistration are delated by an event loop task scheduling. When a domain socket is closed, it's file descriptor might be reused
quickly and therefore trigger a new channel registration using the same descriptor.

Consequently the KQueueEventLoop#add(AbstractKQueueChannel) method will overwrite the current inactive channels having the same descriptor
and the delayed KQueueEventLoop#remove(AbstractKQueueChannel) will remove the active channel that replaced the inactive one.

As active channels are registered, events for this file descriptor won't be processed anymore and the channels will never be closed.

The same problem can also happen in EpollEventLoop. Beside this we also may never remove the AbstractEpollChannel from the internal map
when it is unregistered which will prevent it from be GC'ed

Modifications:

- Change logic of native KQueue and Epoll implementations to ensure we correctly handle the case of FD reuse
- Only try to update kevent / epoll if the Channel is still open (as otherwise it will be handled by kqueue / epoll itself)
- Correctly remove AbstractEpollChannel from internal map in all cases
- Make implementation of closeAll() consistent for Epoll and KQueueEventLoop

Result:

KQueue and Epoll native transports correctly handle FD reuse

Co-authored-by: Norman Maurer <norman_maurer@apple.com>
2019-05-22 09:23:09 +02: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 Always include classes from all native transports no matter on which platfrom netty-all is build (#9111) 2019-04-30 23:23:48 +02:00
bom [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
buffer Prefer direct io buffers if direct buffers pooled (#9167) 2019-05-22 07:32:41 +02:00
codec Only use static Exception instances when we can ensure addSuppressed … (#9152) 2019-05-17 22:23:02 +02:00
codec-dns Add support for TCP fallback when we receive a truncated DnsResponse (#9139) 2019-05-17 14:37:11 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-http Format code to align unaligned code. (#9062) 2019-05-20 12:07:02 +02:00
codec-http2 Only use static Exception instances when we can ensure addSuppressed … (#9152) 2019-05-17 22:23:02 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
common Only use static Exception instances when we can ensure addSuppressed … (#9152) 2019-05-17 22:23:02 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
docker Update to latest JDK13 EA release (#9166) 2019-05-21 20:10:09 +02:00
example Allow to specify KeyStore type in SslContext (#9003) 2019-05-10 07:29:14 +02:00
handler Log deprecation info message when using 'io.netty.handler.ssl.openssl.useKeyManagerFactory' and ignore it when using BoringSSL (#9162) 2019-05-22 08:40:19 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +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 2019-04-30 16:42:29 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
resolver-dns Only try to use reflection to access default nameservers when using Java8 and lower (#9157) 2019-05-18 08:21:33 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
testsuite KQueueEventLoop | EpollEventLoop may incorrectly update registration when FD is reused. 2019-05-22 09:23:09 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
testsuite-native-image [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
transport Only use static Exception instances when we can ensure addSuppressed … (#9152) 2019-05-17 22:23:02 +02:00
transport-native-epoll KQueueEventLoop | EpollEventLoop may incorrectly update registration when FD is reused. 2019-05-22 09:23:09 +02:00
transport-native-kqueue KQueueEventLoop | EpollEventLoop may incorrectly update registration when FD is reused. 2019-05-22 09:23:09 +02:00
transport-native-unix-common Only use static Exception instances when we can ensure addSuppressed … (#9152) 2019-05-17 22:23:02 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +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 .gitignore for docker-sync stuff 2019-03-19 14:03:15 +01: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 [maven-release-plugin] prepare for next development iteration 2019-04-30 16:42:29 +00: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.