andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,052 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
5b2bdd844d
Go to file
Norman Maurer 5b2bdd844d [#2662] Fix race in cancellation of TimerTasks which could let to NPE 
Motivation:

Due some race-condition while handling canellation of TimerTasks it was possibleto corrupt the linked-list structure that is represent by HashedWheelBucket and so produce a NPE.

Modification:

Fix the problem by adding another MpscLinkedQueue which holds the cancellation tasks and process them on each tick. This allows to use no synchronization / locking at all while introduce a latency of max 1 tick before the TimerTask can be GC'ed.

Result:

No more NPE
2014-07-25 06:34:35 +02:00
all [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
buffer Small performance improvements 2014-07-20 09:26:04 +02:00
codec [#2705] Call fireChannelReadComplete() if channelActive(...) decodes messages in ReplayingDecoder / ByteToMessageDecoder 2014-07-24 14:38:46 +02:00
codec-dns Overall cleanup of codec-dns 2014-07-23 14:40:52 -07:00
codec-haproxy Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-http SPDY: fix pushed response NullPointerException 2014-07-21 07:54:15 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-mqtt Fix NPE problems 2014-07-20 12:55:22 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
codec-stomp Fix NPE problems 2014-07-20 12:55:22 +02:00
common [#2662] Fix race in cancellation of TimerTasks which could let to NPE 2014-07-25 06:34:35 +02:00
example Move generic code to HttpOrSpdyChooser to simplify implementations 2014-07-07 09:37:10 +02:00
handler [#2675] Replace synchronization performed on util.concurrent instance in TrafficCounter 2014-07-21 08:23:24 +02:00
license Implemented a Bzip2Encoder 2014-07-17 16:19:39 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
testsuite [#2647] Respect IOV_MAX when call writev in native transport 2014-07-09 12:21:58 +02:00
transport Updated the ChannelGroup JavaDoc by removing b.releaseExternalResources(); 2014-07-24 10:55:09 +02:00
transport-native-epoll [#2685] Epoll transport should use GetPrimitiveArrayCritical / ReleasePrimitiveArrayCritical 2014-07-21 07:11:37 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-07-04 17:26:02 +09:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +09: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 Implemented a Bzip2Encoder 2014-07-17 16:19:39 +02:00
pom.xml Implemented LZF compression codec 2014-07-17 07:18:07 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +09: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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.