b2f1ef57c8
Motivation: AddressResolverGroup adds a listener to the termination future of an EventExecutor when a new AddressResolver is created. The listener calls AddressResolver.close() when the EventExecutor is terminated to give the AddressResolver a chance to release its resources. When using DnsAddressResolverGroup, the AddressResolver.close() will eventually trigger DnsNameResolver.close(), which closes its underlying DatagramChannel. DatagramChannel.close() (or any Channel.close()) will travel through pipeline and trigger EventExecutor.execute() because DnsNameResolver.close() has been invoked from a non-I/O thread. (NB: A terminationFuture is always notified from the GlobalEventExecutor thread.) However, because we are doing this in the listener of the termination future of the terminated EventLoop we are trying to execute a task upon, the attempt to close the channel fails due to RejectedExecutionException. Modifications: - Do not call Channel.close() in DnsNameResolver.close() if the Channel has been closed by EventLoop already Result: No more RejectedExecutionException when shutting down an event loop. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-dns | ||
| codec-haproxy | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-mqtt | ||
| codec-redis | ||
| codec-smtp | ||
| codec-socks | ||
| codec-stomp | ||
| codec-xml | ||
| common | ||
| example | ||
| handler | ||
| handler-proxy | ||
| license | ||
| microbench | ||
| resolver | ||
| resolver-dns | ||
| tarball | ||
| testsuite | ||
| testsuite-osgi | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .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
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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
Development of all 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.