Scott Mitchell e3925be907 HTTP/2 Unit Tests EventLoopGroup cleanup
Motivation:
The HTTP/2 unit tests are suffering from OOME on the master branch.
These unit tests allocating a large number of threads (~706 peak live) which may
be related to this memory pressure.

Modifications:
Each EventLoopGroup shutdown operation will have a `sync()` call.

Result:
Lower peek live thread count and less associated memory pressure.
2014-09-17 12:54:25 -04:00
2014-09-15 15:14:15 +02:00
2014-07-20 12:55:08 +02:00
2014-09-14 08:43:13 -04:00
2014-07-20 12:55:08 +02:00
2014-08-20 06:54:55 +02:00
2014-09-14 08:43:13 -04:00
2014-09-15 15:14:15 +02:00
2009-03-04 10:33:09 +00:00
2013-03-11 09:55:43 +09:00
2009-08-28 07:15:49 +00:00
2014-09-15 15:14:15 +02:00
2014-09-15 15:14:15 +02:00
2014-08-30 13:41:07 -04: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

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.

Description
No description provided
Readme 84 MiB
Languages
Java 99.8%
Shell 0.1%