-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: Other, OS: Linux
Hello! I am using Hudson on an ARM machine using openjdk. Surprisingly
everything works quite well. However if I try to use the --daemon option, then I
get a traceback:
hudson@debian:~$ java -jar hudson.war --daemon
Forking into background to run as a daemon.
Use --logfile to redirect output to a file
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at Main.main(Main.java:59)
Caused by: java.lang.UnsatisfiedLinkError: jnidispatch
(/com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path
at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:568)
at com.sun.jna.Native.loadNativeLibrary(Native.java:550)
at com.sun.jna.Native.<clinit>(Native.java:87)
at com.sun.akuma.CLibrary.<clinit>(CLibrary.java:37)
at com.sun.akuma.JavaVMArguments.currentLinux(JavaVMArguments.java:79)
at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:69)
at com.sun.akuma.Daemon.daemonize(Daemon.java:77)
at com.sun.akuma.Daemon.all(Daemon.java:59)
... 5 more
hudson@debian:~$ java -jar hudson.war --daemon --logfile hudson.log
Forking into background to run as a daemon.
Use --logfile to redirect output to a file
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at Main.main(Main.java:59)
Caused by: java.lang.UnsatisfiedLinkError: jnidispatch
(/com/sun/jna/linux-arm/libjnidispatch.so) not found in resource path
at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:568)
at com.sun.jna.Native.loadNativeLibrary(Native.java:550)
at com.sun.jna.Native.<clinit>(Native.java:87)
at com.sun.akuma.CLibrary.<clinit>(CLibrary.java:37)
at com.sun.akuma.JavaVMArguments.currentLinux(JavaVMArguments.java:79)
at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:69)
at com.sun.akuma.Daemon.daemonize(Daemon.java:77)
at com.sun.akuma.Daemon.all(Daemon.java:59)
... 5 more
I just picked the javanet subcomponent since I had to pick one and it seemed the
most appropriate. Googling for "UnsatisfiedLinkError jnidispatch" generates some
potentially useful reports within other projects.
- is related to
-
JENKINS-24521 Update jna from 3.3.0-jenkins to 4.1.0 (or newer)
- Resolved