JNA native support (/com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path

Asked 31/1, 2013 at 22:3 Answered 31/8, 2020 at 22:51

I have started to build a java service which incorporates JNA to load a native C/C++ lib and i want to run the java service on the Raspberry PI aka arm platform. I have successfully built a stable ground of the service and it runs on both Windows7 and linux-amd64/debian but.. on the RPI platform i get the above stated error: Exception in thread "main" java.lang.UnsatisfiedLinkError: JNA native support (/com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path

On the RPI i have done the following: * Installed both openjdk7 and java8 beta with arm hard float support. * Installed libjna-java lib.

Following are set:

Java

root@pisces:/opt/TellstickReplay# java -version
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b36e)
Java HotSpot(TM) Client VM (build 25.0-b04, mixed mode)
root@pisces:/opt/TellstickReplay#

LD_LIBRARY_PATH

root@pisces:/opt/TellstickReplay# echo $LD_LIBRARY_PATH
/opt/lib/jna

CLASSPATH

root@pisces:/opt/TellstickReplay# echo $CLASSPATH
/usr/lib/jna

None of the settings seems to satisfy JAVA with JNA support. I have even tried to export both jna.jar and linux-arm.jar into the project in Eclipse and all together rebuild the jars into the exported jar still getting the same error. The exported jar has been tested successfully on both windows and linux so the jar file is working.

I have also tried to just use CLASSPATH in the Manifest in the jar file but with no success. I have also tried to explicitly load the libjnidispatch.so from the absolute path but JAVA then starts to complain that it cannot find the file to libjnidispatch.so even that the path is 100% correct.

So.. does anyone know HOW to correctly get JNA support on the Raspberry PI platform to work?? Please, im getting tremendously frustrated and soon giving up hope to fix this..

Rogan answered 31/1, 2013 at 22:3 Comment(1)

Possible candidate for raspberrypi.stackexchange.com – Griner 31/1, 2013 at 22:6

Where is libjnidispatch.so on your system? If it's not on your system, JNA will attempt to unpack it from jna.jar from the indicated resource path. If it's not there either, you'll get the UnsatisfiedLinkError.

It's recommended that you explicitly install libjnidispatch.so on your system where possible; the jna.jar bundling is mostly there to facilitate usage on the more common desktop platforms.

linux-arm.jar contains the most recent build of libjnidispatch.so, but only WebStart knows how to automatically load the native from a jar like that. If you unpack it into /opt/lib/jna (or elsewhere on LD_LIBRARY_PATH), you should avoid the link error.

Ipoh answered 1/2, 2013 at 16:16 Comment(19)

the libjnidispatch.so is both in the CLASSPATH, LD_LIBRARY_PATH and on the filesystem in /usr/libs/jna. – Manta 1/2, 2013 at 20:17

The error message indicates that JNA has tried to unpack it from jna.jar after unsuccessfully loading via System.loadLibrary(). You can set the system property jna.boot.library.path to /usr/libs/jna, but you shouldn't have to if LD_LIBRARY_PATH already includes that path (note that in your question you have it set to /*opt/lib*/jna, which will result in an error if the library is actually in /*usr/libs*/jna). – Ipoh 1/2, 2013 at 20:37

You mention System.loadLibrary() though i have read about JNA using Native.loadLibrary() but looking through jna i can´t find System.loadLibrary(). Is there a significant difference between these two?? – Manta 1/2, 2013 at 20:59

Also is there a Raspbian image that have JNA working out of the box? I have been searching for a solution for this for so long i cant really motivate finding the source for this. – Manta 1/2, 2013 at 21:24

im trying to load a C library: this.libTelldus = (CLibrary)Native.loadLibrary("telldus-core", CLibrary.class); but i keep getting constant UnsatisfiedLinkError all the time. I have changed the LD_LIBRARY_PATH to /opt/lib/jna and CLASSPATH to /opt/lib/jna and trying to use -Djna.boot.library.path=/opt/lib/jna. – Manta 1/2, 2013 at 21:28

Exception in thread "main" java.lang.UnsatisfiedLinkError: JNA native support (/com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path – Manta 1/2, 2013 at 22:6

JNA uses System.loadLibrary() within Native.loadLibrary(). Does /opt/lib/jna/libjnidispatch.so exist and is it a valid linux-arm shared library? You can build jna.jar yourself on a self-hosted linux-arm platform (you could probably cross-compile, but that'd take some configuration tweaking of the build.xml and Makefile). I would guess, though that the debian linux-arm build should be perfectly compatible with the raspberry pi. – Ipoh 1/2, 2013 at 23:5

Yes i have placed the libjnidispatch.so in /op/lib/jna but what i dont understand if its linked or not. Should there be a symlink to /usr/lib? So it could be that im missing the libjnidispatch.so as a shared library?? – Manta 2/2, 2013 at 8:3

Have i placed the .so file in the wrong directory? Should it be placed elsewere? Or is it possible to load the damn lib from java so it knows its there??? – Manta 2/2, 2013 at 8:36

It should be possible to load libjnidispatch.so from anywhere. What does file libjnidispatch.so report? – Ipoh 2/2, 2013 at 10:44

hmm it didnt report anything actually. shouldnt be a symlink showing? – Manta 2/2, 2013 at 14:10

sorry that was find, my misstake. file libjnidispatch.so returns: pi@raspberrypi /opt/lib/jna $ file libjnidispatch.so libjnidispatch.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xb2fe121fc0b27c6562e0a73bda21e2bc23193938, not stripped – Manta 2/2, 2013 at 14:19

Run with system property jna.nounpack=true, which may provide more detail on the library load failure. – Ipoh 2/2, 2013 at 15:23

I found the problem. JNA.jar was actually missing libjnidispatch.so inside the jna.jarso i just build jna.jar with Ant on the Raspberry Pi with openjdk6 and that solved the problem. Its strange though that linking with -Djna.boot.librar.path=/path/to/libjnidispatch.so still got the UnsatisfiedLinkError. Oh well, it works now =) Thank you very much for your patiance and input!! – Manta 2/2, 2013 at 18:25

jna.boot.library.path (just like LD_LIBRARY_PATH) has to be a path (directories only), not the filename path. glad you got it working. – Ipoh 2/2, 2013 at 20:29

@Pär Fransman - do you just use ant command inside JNA source downloaded from GitHub? or is there some special config/argument needed? I have the same problem with Processing on Raspberry Pi as you described, but when I compile JNA, it leads to another problem – Hemangioma 28/4, 2013 at 21:2

My error after compiling JNA with ant and copying jna.jar to Processing dir is: can't obtain newinstance method for class com.sun jna.structure. Any ideas? – Hemangioma 28/4, 2013 at 22:37

Post full details to the JNA user's list. – Ipoh 29/4, 2013 at 13:43

@PärFransman it would be nice if you could post your own answer, it makes it easier for people like me to find it – Freer 21/11, 2013 at 9:10

I am re-compiling Apache Spark for RPI2 and I've spent a couple of days to fix the issue. Then I've found the easiest possible solution. All you need to have is a libjnidispatch.so link in your default JVM's native lib path.

sudo -s ln -s /usr/lib/arm-linux-gnueabihf/jni/libjnidispatch.so /usr/lib/jvm/default-java/jre/lib/arm/libjnidispatch.so

Tamatave answered 11/6, 2015 at 18:28 Comment(2)

It almost worked and what I have discovered is that Elasticsearch 7.1.0 needs libjna-jni at least 5.2.0 andd the latest version for Raspberry Pi is 4.2.2 – Vitals 23/5, 2019 at 1:2

The solution that worked for me was finding the relevant libjni.*.so library file and adding it to the jna.x.x.ja file. – Vitals 23/5, 2019 at 2:57

I packaged the new jna.jar (4.0) and it includes the linux-arm/libjnidispatch.so. The code I was trying to run now works.

Seasonal answered 16/1, 2014 at 0:16 Comment(0)

I'd say its more of "glitch of configuration of the location for the "libjnidispatch.so" in the OS your using or that particular JRE systems internal folder/package/JNDI-structure, it may not be an identically laid out Debian or Java JRE.

Recommended topics

Hot tags