NPE in NetworkUtils.determineAnyAddress

Was told by a friend that he sees an NPE in his setup (details to follow):

20200321-185106.688 18:51:06.681 [org.jitsi.impl.osgi.framework.AsyncExecutor] ERROR org.jitsi.impl.osgi.framework.BundleImpl - Error starting bundle: net.java.sip.communicator.impl.netaddr.NetaddrActivator@fd79e60
20200321-185106.688 java.lang.ExceptionInInitializerError: null
20200321-185106.688     at net.java.sip.communicator.util.NetworkUtils.determineAnyAddress(NetworkUtils.java:1149) ~[jitsi-util-2.13.f6042d3.jar!/:?]	<--!!!!!!!!!!!!!!!!!!!
20200321-185106.688     at net.java.sip.communicator.util.NetworkUtils.<clinit>(NetworkUtils.java:62) ~[jitsi-util-2.13.f6042d3.jar!/:?]
20200321-185106.688     at net.java.sip.communicator.impl.netaddr.NetworkAddressManagerServiceImpl.initRandomPortSocket(NetworkAddressManagerServiceImpl.java:433) ~[jitsi-netaddr-2.13.f6042d3.jar!/:?]
20200321-185106.689     at net.java.sip.communicator.impl.netaddr.NetworkAddressManagerServiceImpl.start(NetworkAddressManagerServiceImpl.java:107) ~[jitsi-netaddr-2.13.f6042d3.jar!/:?]
20200321-185106.689     at net.java.sip.communicator.impl.netaddr.NetaddrActivator.start(NetaddrActivator.java:89) ~[jitsi-netaddr-2.13.f6042d3.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:307) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:472) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:137) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:122) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:28) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689     at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:231) [jitsi-android-osgi-1.0-20180322.162617-2.jar!/:?]
20200321-185106.689 Caused by: java.lang.NullPointerException
20200321-185106.690     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1847) ~[?:1.8.0_242]
20200321-185106.690     at java.lang.Runtime.loadLibrary0(Runtime.java:871) ~[?:1.8.0_242]
20200321-185106.690     at java.lang.System.loadLibrary(System.java:1124) ~[?:1.8.0_242]
20200321-185106.690     at java.net.NetworkInterface$1.run(NetworkInterface.java:59) ~[?:1.8.0_242]
20200321-185106.690     at java.net.NetworkInterface$1.run(NetworkInterface.java:57) ~[?:1.8.0_242]
20200321-185106.690     at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_242]
20200321-185106.690     at java.net.NetworkInterface.<clinit>(NetworkInterface.java:56) ~[?:1.8.0_242]
20200321-185106.690     ... 11 more
20200321-185106.693 18:51:06.692 [org.jitsi.impl.osgi.framework.AsyncExecutor] ERROR org.jitsi.impl.osgi.framework.launch.FrameworkImpl - Error changin

[ibauersachs]

Okay, so this is probably caused by illegal reflection somwhere in Ofmeet. See e.g. these bug reports for 8u242:

• https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-January/011026.html
• https://bugzilla.redhat.com/show_bug.cgi?id=1805105

I see the same JDK-internal field being accessed by multiple Igniterealtime libs: https://github.com/search?q=org%3Aigniterealtime+sys_paths&type=Code (some of this code is 15 years old)

This is not a Jitsi issue. Please report this to the respective projects at igniterealtime, @guusdk might point to the right people.

[gjaekel]

Damn!

I just was supporting some OpenFire user who installed this application on a fresh VM using Ubuntu20. Currently this provide OpenJDK11.0.9+11, and here the same regression occurs!

OpenJDK Runtime Environment (build 11.0.9+11-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.9+11-Ubuntu-0ubuntu1.20.04, mixed mode)

This user switched to Java8u272 and try some Jav14, also. With both, the problem vanish!