Go to file
Norman Maurer 3543e17967
Ensure OpenSslEngine will not try to call SSL_free multiple times even when constructor throws. (#8399)
Motivation:

When the constructor of OpenSslEngine threw we could end up to self call SSL_free by ourself and then have the finalizer do the same which may lead to double free-ing and so SIGSEV.

Modifications:

Just call shutdown() when the constructor throws and so ensure SSL_free is guarded correctly in the finalizer.

Result:

No more SIGSEV possible.
2018-10-18 07:38:03 +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-09-27 19:00:45 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
buffer Simplify ByteBufInputStream.readLine() logic (#8380) 2018-10-13 06:24:40 +02:00
codec [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-http2 Notify http2 error handler before closeStreamLocal on HEADERS write failure (#8332) 2018-09-28 10:29:12 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
common deprecate own ConcurrentSet for removal (#8340) 2018-10-15 19:36:05 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
docker When running our testsuite with netty-tcnative-boringssl-static we should use an empty classifier. (#8396) 2018-10-17 19:36:20 +02:00
example [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
handler Ensure OpenSslEngine will not try to call SSL_free multiple times even when constructor throws. (#8399) 2018-10-18 07:38:03 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +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-09-27 19:00:45 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
resolver-dns Correctly parse /etc/resolv.conf when contain multiple entries for searchdomain. (#8351) 2018-10-12 05:00:32 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
testsuite Add support for TLSv1.3 (#8293) 2018-10-17 08:35:35 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
testsuite-http2 Upgrade h2spec-maven-plugin (#8386) 2018-10-16 07:05:45 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
transport Increase test timeout (#8385) 2018-10-15 15:10:22 +02:00
transport-native-epoll epoll_wait produces an EINVAL error since 4.1.30 (#8350) 2018-10-12 05:02:41 +02:00
transport-native-kqueue Use MACOSX_DEPLOYMENT_TARGET=10.6 when compile native transport on MacOS (#8379) 2018-10-13 04:25:56 +02:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-09-27 19:00:45 +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 Add support for TLSv1.3 (#8293) 2018-10-17 08:35:35 +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.