andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
8,563 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
661bd86829
Go to file
Norman Maurer 661bd86829 Fix flacky test introduced by af2f343648 
Motivation:

af2f343648 introduced a test-case which was flacky due of multiple problems:

- we called writeAndFlush(...) in channelRead(...) and assumed it will only be called once. This is true most of the times but it may be called multile times if the data is fragemented.
- we didnt guard against the possibility that channelRead(...) is called with an empty buffer

Modifications:

- Call writeAndFlush(...) in channelActive(...) so we are sure its only called once and close the channel once we wrote the data
- only compare the data after we received a close so we are sure there isnt anything extra received
- check for exception and if we catched one fail the test.

Result:

No flacky test anymore and easier to debug issues that accour because of a catched exception.
2017-12-15 13:09:17 +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-08 09:26:15 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
buffer Reduce Object allocations in CompositeByteBuf. 2017-12-12 09:08:58 +01:00
codec [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
common SingleThreadEventExecutor ignores startThread failures 2017-12-14 21:38:37 +00:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
handler [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +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 [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
testsuite Fix flacky test introduced by af2f343648 2017-12-15 13:09:17 +01:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
transport [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
transport-native-epoll FileDescriptor writev core dump 2017-12-14 16:47:31 -08:00
transport-native-kqueue FileDescriptor writev core dump 2017-12-14 16:47:31 -08:00
transport-native-unix-common FileDescriptor writev core dump 2017-12-14 16:47:31 -08:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +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 [maven-release-plugin] prepare for next development iteration 2017-12-08 09:26:15 +00: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

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

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.