netty5/transport-native-kqueue
Norman Maurer 3f101caa4c Not call java methods from within JNI init code to prevent class loading deadlocks.
Motivation:

We used NetUtil.isIpV4StackPreferred() when loading JNI code which tries to load NetworkInterface in its static initializer. Unfortunally a lock on the NetworkInterface class init may be already hold somewhere else which may cause a loader deadlock.

Modifications:

Add a new Socket.initialize() method that will be called when init the library and pass everything needed to the JNI level so we not need to call back to java.

Result:

Fixes [#7458].
2017-12-06 14:34:15 +01:00
..
src Not call java methods from within JNI init code to prevent class loading deadlocks. 2017-12-06 14:34:15 +01:00
pom.xml Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00