Go to file
Norman Maurer 1b383c5de8 Correctly handle errors when using OpenSSL
Motivation:

We used ERR_get_error() to detect errors and missed to handle different errors. Also we missed to clear the error queue for a thread before invoke SSL operations,
this could lead to detecting errors on different OpenSslEngines then the one in which the error actual happened.

Modifications:

Explicit handle errors via SSL.get_error and clear the error code before SSL operations.

Result:

Correctly handle errors and no false-positives in different OpenSslEngines then the one which detected an error.
2015-06-21 21:07:12 +02:00
all Backport codec-haproxy 2015-06-04 19:26:50 +02:00
buffer [#3888] Use 2 * cores as default minimum for pool arenas. 2015-06-18 07:19:15 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
codec-haproxy Backport codec-haproxy 2015-06-04 19:26:50 +02:00
codec-http Ensure no null values are used when add/set headers. 2015-06-08 09:33:28 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
common Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
example Replace SpdyOrHttpChooser and Http2OrHttpChooser with ApplicationProtocolNegotiationHandler 2015-06-05 14:51:21 +09:00
handler Correctly handle errors when using OpenSSL 2015-06-21 21:07:12 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
testsuite More meaningful assertion failure message 2015-06-04 12:08:49 +09:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport Fix broken constructor chaining for FixedChannelPool class. 2015-06-18 20:11:41 +02:00
transport-native-epoll [#3848] Respect EPOLLERR event 2015-06-06 10:34:36 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04: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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Correctly handle errors when using OpenSSL 2015-06-21 21:07:12 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09: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 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.