andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,806 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
a31f36d933
Go to file
Trustin Lee a31f36d933 Stop ThreadLocalRandom's initial seed generation immediately on interruption 
Motivation:

ThreadLocalRandomTest reveals that ThreadLocalRandom's initial seed generation loop becomes tight if the thread is interrupted.
We currently interrupt ourselves inside the wait loop, which will raise an InterruptedException again in the next iteration, resulting in infinite (up to 3 seconds) exception construction and thread interruptions.

Modification:

- When the initial seed generator thread is interrupted, break out of the wait loop immediately.
- Log properly when the initial seed generation failed due to interruption.
- When failed to generate the initial seed, interrupt the generator thread just in case the SecureRandom implementation handles it properly.
- Make the initial seed generator thread daemon and handle potential exceptions raised due to the interruption.

Result:

No more tight loop on interruption.  More robust generator thread termination. Fixes #2412
2014-04-20 17:55:25 +09:00
all Ensure native transport is included in all and tarball 2014-02-17 22:46:07 +01:00
buffer Fix error that causes (up to) double memory usage 2014-04-15 07:03:13 +02:00
codec Fix chunk type for stream identifier 2014-04-19 21:06:28 +02:00
codec-http [#2401] Improve documentation of HttpObjectAggregator 2014-04-17 15:45:00 +02:00
codec-memcache [codec-memcache] Simplify object hierachy and remove Headers. 2014-03-04 13:05:30 +01:00
codec-socks Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
common Stop ThreadLocalRandom's initial seed generation immediately on interruption 2014-04-20 17:55:25 +09:00
example SPDY: refactor frame codec implementation 2014-04-15 19:57:38 +02:00
handler Feed only a single SSL record to SSLEngine.unwrap() 2014-04-20 17:33:04 +09:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 13:28:37 +01:00
microbench Upgrade JMH to 0.4.1 and make use of @Params. 2014-02-23 16:39:39 +01:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite [#2375] [#2404] Fix bug in respecting ChannelConfig.setAutoRead(false) and also fix Channel.read() for OIO 2014-04-17 07:50:51 +02:00
transport Move validatePromise(...) to ChannelHandlerInvokerUtil. Related to [#2398] 2014-04-17 16:01:26 +02:00
transport-native-epoll Fix buffer leak in EpollDatagramChannel 2014-04-18 20:37:52 +02:00
transport-rxtx Apply receive timeout to commPort when using RxtxChannel. Part of [#1390] 2014-02-23 16:31:34 +01:00
transport-sctp [#2375] [#2404] Fix bug in respecting ChannelConfig.setAutoRead(false) and also fix Channel.read() for OIO 2014-04-17 07:50:51 +02:00
transport-udt Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08: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:04:38 +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:13: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:28:37 +01:00
pom.xml Add -verbose:gc option for test runs 2014-03-17 14:17:08 +09:00
README.md Update README.md 2014-01-16 14:38:36 +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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.