andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,764 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
cd579f75d2
Go to file
Norman Maurer cd579f75d2 [#2363] SelectedSelectionKeySet may hold strong reference to SelectionKey after Channel is closed 
Motivation:
Because we not null out the array entry in the SelectionKey[] which is produced by SelectedSelectionKeySet.flip() we may end up with a few SelectionKeyreferences still hanging around here even after the Channel was closed. As these entries may be present at the end of the SelectionKey[] which is never updated for a long time as not enough SelectionKeys are ready.

Modifications:
Once we access the SelectionKey out of the SelectionKey[] we directly null it out.

Result:
Reference can be GC'ed right away once the Channel was closed.
2014-04-05 19:27:09 +02:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:33 +01:00
buffer Implement Thread caches for pooled buffers to minimize conditions. This fixes [#2264] and [#808]. 2014-03-20 09:31:15 -07:00
codec [#2339] Reduce memory usage in ProtobufVarint32LengthFieldPrepender 2014-03-28 20:29:46 +01:00
codec-http Adding origins whitelist support for CORS 2014-03-30 19:40:59 +02:00
codec-http2 First round of cleanup codec-http2 2014-04-05 16:17:42 +02:00
codec-memcache [codec-memcache] Simplify object hierachy and remove Headers. 2014-03-04 13:04:44 +01:00
codec-socks Fix an inspector warning 2014-02-06 15:03:03 -08:00
common Fixing spelling/typo in javadocs for EventExecutor. 2014-03-23 16:29:51 +01:00
example Adding origins whitelist support for CORS 2014-03-30 19:40:59 +02:00
handler [#2358] SslHandler.safeClose(...) may not notify the ChannelPromise 2014-04-03 13:30:05 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:15 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Perform cross-tests between NIO and epoll transport 2014-03-17 10:49:31 +09:00
transport [#2363] SelectedSelectionKeySet may hold strong reference to SelectionKey after Channel is closed 2014-04-05 19:27:09 +02:00
transport-native-epoll [#2359] EpollSocketChannel.remoteAddress0() is always null on accepted EpollSocketChannels 2014-04-04 15:52:29 +02:00
transport-rxtx Apply receive timeout to commPort when using RxtxChannel. Part of [#1390] 2014-02-23 16:35:35 +01:00
transport-sctp Directly use memory addresses for gathering writes to reduce gc pressure. Part of [#2239] 2014-02-21 14:16:37 +01:00
transport-udt Enable a user specify an arbitrary information with ReferenceCounted.touch() 2014-01-29 11:44:59 +09:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:03:43 +01: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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:56:15 +01:00
pom.xml First cut of frame encoding/decoding and session management for HTTP2 2014-03-27 10:40:47 -07:00
README.md Fix the 'branches to look' section 2014-01-16 14:37:54 +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.