Go to file
Thomas Devanneaux 3ae57cf302 ByteBuf.toString(Charset) is not thread-safe
Motivation:

Calling ByteBuf.toString(Charset) on the same buffer from multiple threads at the same time produces unexpected results, such as various exceptions and/or corrupted output. This is because ByteBufUtil.decodeString(...) is taking the source ByteBuffer for CharsetDecoder.decode() from ByteBuf.internalNioBuffer(int, int), which is not thread-safe.

Modification:

Call ByteBuf.nioBuffer() instead of ByteBuf.internalNioBuffer() to get the source buffer to pass to CharsetDecoder.decode().

Result:

Fixes the possible race condition.
2018-01-21 09:02:42 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
buffer ByteBuf.toString(Charset) is not thread-safe 2018-01-21 09:02:42 +01:00
codec Cleanup: replaced deprecated ctx.attr() and ctx.hasAttr() methods usage with ch.attr() and ch.hasAttr(). 2018-01-18 15:00:41 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-http Fix DefaultHttpDataFactory cleanup bug 2017-12-28 07:40:17 +01:00
codec-http2 HpackDecoderTest cleanup 2018-01-19 17:26:06 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
common ObjectCleaner should continue cleaning despite exceptions 2018-01-19 20:09:20 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
handler Cleanup: replaced deprecated ctx.attr() and ctx.hasAttr() methods usage with ch.attr() and ch.hasAttr(). 2018-01-18 15:00:41 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Fixed JMH ByteBuf benchmark to avoid dead code elimination 2017-12-19 14:09:18 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
resolver-dns Fix concurrency issue in DnsNameResolver when DefaultDnsCache is used. 2018-01-17 06:08:36 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
testsuite Remove remote initiated renegotiation support 2018-01-15 10:16:08 +01:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
testsuite-http2 Fix h2spec test 4.3 about invalid header block 2018-01-18 11:01:20 -08:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport Fail fast when DefaultChannelPromise is constructed with null as Channel. 2018-01-18 18:57:42 +00:00
transport-native-epoll IovArray#add return value resulted in more ByteBufs being added during iteration 2018-01-04 08:04:32 -08:00
transport-native-kqueue IovArray#add return value resulted in more ByteBufs being added during iteration 2018-01-04 08:04:32 -08:00
transport-native-unix-common IovArray#add return value resulted in more ByteBufs being added during iteration 2018-01-04 08:04:32 -08:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-12-15 13:10:54 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Test output should include GC details 2017-12-22 19:31:20 +01:00
README.md Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +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.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.