2b16d9f670
Related issue: #2093 Motivation: When a channel with SslHandler is closed with pending writes (either unencrypted or encrypted), SslHandler.channelClosed() attempts to acquire a lock and fail the futures of the pending writes. If a user added a listener to any of the failed futures and the listener attempts to write something, it will make SslHandler.handleDownstream() invoked, which also attempts to acquire the same lock. Because the lock is non-reentrant, even if these two lock acquisitions are taking place in the same thread, the second attempt will block for ever. Modification: Do not fail the futures while holding a lock. Notify them after releasing the lock. Result: One less dead lock |
||
|---|---|---|
| license | ||
| src | ||
| .fbfilter.xml | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
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.