Yet Another Java Service Wrapper / Bugs / #93 UnsatisfiedLinkError for genconfig fails on arm

rzo - 2013-12-20

hello,

yajsw currently uses jna-3.5.1
this version does not include a linux-arm library
i will update jna with the next release.

you may try adding the according native library into the current jar of jna

see: http://stackoverflow.com/questions/14635999/jna-native-support-com-sun-jna-linux-arm-libjnidispatch-so-not-found-in-resou

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2013-12-20

ps: try replacing the following jar in the yajsw distr

https://dl.dropboxusercontent.com/u/20584933/yajsw/jna-3.5.1.jar

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas - 2014-01-06

Thank you for the response, I will try the proposals.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2014-01-06

hello,

jna-3.5.1 will not work.
i will have to update yajsw to support it.
however you can try the following workaround:

@see http://stackoverflow.com/questions/14635999/jna-native-support-com-sun-jna-linux-arm-libjnidispatch-so-not-found-in-resou

from the jna jar copy the file from the folder com/sun/jna/linux-arm to /opt/lib/jna (or elsewhere on LD_LIBRARY_PATH)

in setenv.sh set the wrapper jvm option -Djna.nounpack=true
and maybe also: -Djna.boot.library.path=/opt/lib/jna

-- Ron

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kidmose - 2014-09-16

I'm trying to apply the fix above, but finding my understanding to be lacking.
Do you care to elaborate a bit/guide me?

I'm using a raspberry pi with 2014-09-09-wheezy-raspbian.
$ uname -a
Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux

I've done the following:
pi@raspberrypi ~ $ cd
pi@raspberrypi ~ $ mkdir tmp
pi@raspberrypi ~ $ cd tmp
pi@raspberrypi ~/tmp $ jar xf ~/<some-app>-server/lib/core/jna/jna-3.4.1.jar com/sun/jna/linux-arm/libjnidispatch.so
pi@raspberrypi ~/tmp $ sudo mkdir -p /opt/lib/jna
pi@raspberrypi ~/tmp $ sudo cp com/sun/jna/linux-arm/libjnidispatch.so /opt/lib/jna/
pi@raspberrypi ~/tmp $ cd ~/<some-app>-server/bin/
pi@raspberrypi ~/<some-app>-server/bin $ cp setenv.sh setenv.sh.bak
pi@raspberrypi ~/<some-app>-server/bin $ sudo chmod -w setenv.sh.bak
pi@raspberrypi ~/<some-app>-server/bin $ editor setenv.sh
pi@raspberrypi ~/<some-app>-server/bin $ diff setenv.sh.bak setenv.sh
34c34
< wrapper_java_sys_options=-Djna_tmpdir="$wrapper_home"/tmp
---
> wrapper_java_sys_options=-Djna_tmpdir="$wrapper_home"/tmp -Djna.nounpack=true -Djna.boot.library.path=/opt/lib/jna

This seems to go wrong, however:
pi@raspberrypi ~/<some-app>-server/bin $ sudo ./setenv.sh
++++++++++ YAJSW SET ENV ++++++++++
./setenv.sh: line 34: -Djna.nounpack=true: command not found
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)
wrapper home : /home/pi/<some-app>-server
configuration: /home/pi/<some-app>-server/conf/wrapper.conf
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)

Any suggestions?
Thank you so much!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kidmose - 2014-09-17

Seems like i got this bit figured out (though I'm now stuck on something else)

In case anyone else is facing the same issues as I was, heres my way arround it:

Extracting com/sun/jna/linux-arm/libjnidispatch.so and placing it where specified with '-Djna.boot.library.path=/opt/lib/jna' didn't solve it for me, so I moved on to compiling it myself.
I realised later that the executable bit for /opt/lib/jna/libjnidispatch.so wasn't set - maybe setting this is enough to make it work.

Transcript of my solution:
pi@raspberrypi ~ $ sudo apt-get install ant libx11-dev libxt-dev
pi@raspberrypi ~ $ wget https://github.com/twall/jna/archive/3.4.1.tar.gz
pi@raspberrypi ~ $ mv 3.4.1.tar.gz jna-3.4.1.tar.gz
pi@raspberrypi ~ $ tar xvzf jna-3.4.1.tar.gz
pi@raspberrypi ~ $ cd jna-3.4.1
pi@raspberrypi ~/jna-3.4.1 $ ant
# jUnit testcases testCallFloatCallback and testCallDoubleCallback fail, causing "BUILD FAILED" messages, disregard
pi@raspberrypi ~/jna-3.4.1 $ sudo mkdir -p /opt/lib/jna
pi@raspberrypi ~/jna-3.4.1 $ sudo cp build/native/libjnidispatch.so /opt/lib/jna/

and then changing the bin/wrapper.sh:
pi@raspberrypi ~/smartamm-server/bin $ diff wrapper.sh.bak wrapper.sh
7c7
< "$java_exe" "$wrapper_java_options" "$wrapper_java_sys_options" -jar $wrapper_jar" "$@"
---
> "$java_exe" "$wrapper_java_options" "-Djna.boot.library.path=/opt/lib/jna" "$wrapper_java_sys_options" -jar "$wrapper_jar" "$@"

I suspect '-Djna...' should be added in bin/setenv.sh instead, but I couldn't figure out how to do that. If you can, I'd like to know how.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2014-09-21

hello,

yajsw-alpha-12.00 should work out of the box on raspberry pi. just tested it on

Raspbian
Debian Wheezy
Version: September 2014

for the service to start on boot you have to set the wrapper.daemon.update_rc property or to invoke

update-rc.d -f <service name=""> remove

to remove the service links and then invoke

update-rc.d <service name=""> defaults

reason: yajsw sets per default the execution order to 20 (eg creates the link rc2.d/S20<name>). for some reason raspbian does not seem to boot the service.

setting the execution order to 01 seems to work.

-- Ron

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2014-09-21

ps: for some reason sourceforge is converting <service name=""> to <service name="">

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kidmose - 2014-09-22

I'm currently using yajsw-stable-11.11, so updating it seems to be a good idea then.
(Sorry, I forgot to mention that earlier)

Do you know, off the top of your head, if 11.11 should be expected to fail at starting the service ('sudo startDaemon.sh') on the pi as well?
(Related to the wrapper.daemon.update_rc property maybe?)

Thank you very much,
Egon

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2015-12-23

status: open --> closed-out-of-date
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rzo - 2015-12-23

works for me on the pi.
pls reopen if you are still having issues.
release 12.04

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

UnsatisfiedLinkError for genconfig fails on arm

Install java, groovy and native applications as services or daemons

Group

Searches

Help

#93 UnsatisfiedLinkError for genconfig fails on arm

Discussion