fc19fce467
Motivation: The logging statements in i.n.u.c.DefaultPromise do not emit the caught Throwable when a Throwable is thrown while a listener is being notified of completed or progressed operations. Modifications: This issue arises because the logging message has a single placeholder but is passing two additional arguments, the second one being the caught Throwable that is thus quietly not logged. We address this by modifying the logging statements to ensure the caught Throwable is logged. In this case, the preferred approach is to use the logger override that accepts a message and a Throwable parameter since logger implementations might have special handling for this case. Result: Log messages from i.n.u.c.DefaultPromise when a Throwable is thrown while notifying a listener of completed or progressed operations will contain the caught Throwable. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-haproxy | ||
| codec-http | ||
| codec-socks | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| 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.