Skip to content
Netty project - an event-driven asynchronous network application framework http://netty.io/
Java C Shell Groovy Protocol Buffer C++
Find file
Latest commit b9682a2 @Scottmitch Scottmitch committed with normanmaurer EPOLL dladdr unexpected return value
Motivation:
netty_epoll_native.c uses dladdr in attempt to get the name of the library that the code is running in. However the address passed to this funciton (JNI_OnLoad) may not be unique in the context of the application which loaded it. For example if another JNI library is loaded this address may first resolve to the other JNI library and cause the path name parsing to fail, which will cause the library to fail.

Modifications:
- Pass an addresses which is local to the current library to dladdr

Result:
EPOLL JNI library can be loaded in an environment where multiple JNI libraries are loaded.
Fixes #4840
Failed to load latest commit information.
all [maven-release-plugin] prepare for next development iteration
buffer [#4841] Fix segfault if UnpooledUnsafeHeapByteBuf.getShort(..) is use…
codec-dns [maven-release-plugin] prepare for next development iteration
codec-haproxy [maven-release-plugin] prepare for next development iteration
codec-http [maven-release-plugin] prepare for next development iteration
codec-http2 [maven-release-plugin] prepare for next development iteration
codec-memcache [maven-release-plugin] prepare for next development iteration
codec-mqtt [maven-release-plugin] prepare for next development iteration
codec-socks [maven-release-plugin] prepare for next development iteration
codec-stomp [maven-release-plugin] prepare for next development iteration
codec-xml [maven-release-plugin] prepare for next development iteration
codec [#4793] Correctly add newlines when encode base64
common Expose Helper to obtain the "best" mac address.
example [maven-release-plugin] prepare for next development iteration
handler-proxy [maven-release-plugin] prepare for next development iteration
handler Allow InputStreams for key/trust managers in SslContextBuilder
license added support for Protobuf codec nano runtime
microbench [maven-release-plugin] prepare for next development iteration
resolver-dns [maven-release-plugin] prepare for next development iteration
resolver [#4834] Fix race in AddressResolverGroup
tarball [maven-release-plugin] prepare for next development iteration
testsuite-osgi [maven-release-plugin] prepare for next development iteration
testsuite [maven-release-plugin] prepare for next development iteration
transport-native-epoll EPOLL dladdr unexpected return value
transport-rxtx [maven-release-plugin] prepare for next development iteration
transport-sctp [maven-release-plugin] prepare for next development iteration
transport-udt [maven-release-plugin] prepare for next development iteration
transport Expose Helper to obtain the "best" mac address.
.fbprefs Updated Find Bugs configuration
.gitignore Add JVM crash logs to .gitignore
.travis.yml Travis CI branch whitelisting
CONTRIBUTING.md Move the pull request guide to the developer guide
LICENSE.txt Relicensed to Apache License v2
NOTICE.txt added support for Protobuf codec nano runtime
README.md Fix the 'branches to look' section
pom.xml Add maven profile to run tests with -Dio.netty.noUnsafe=true
run-example.sh Add HTTP/2 Netty tiles example

README.md

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:

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.

Something went wrong with that request. Please try again.