New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.UnsatisfiedLinkError: org.fusesource.lmdbjni.JNI.init() #38
Comments
Interesting use case. There shouldn't be any difference. Are you sure lmdbjni-linux64 is on classpath? You can try enable |
Here is what I get with [Loaded org.fusesource.lmdbjni.NativeObject from file:/*.jar] I don't see lmdbjni-linux64 but in my build.sbt I do have it . |
I able to make it works by loading lmdbjni explicitly in my code with |
It probably means that sbt screw up your classpath somehow. You could try debug-step through Would be interesting to hear why it wont load automatically. |
In my build.sbt I have the following line :
I don't really understand how it works but META-INF is discarded. Maybe it make sbt to screw up the classpath ? |
Yes, probably. I haven't used sbt, but maybe its removed by the deduplication mechanism? |
Did you manage to find the problem? |
No, still searching for a solution. |
Are you still searching? Otherwise I would like to close this issue. |
Closing. Inactivity. |
For the benefit of people who find this issue searching (like I did). The problem is that Spark (or maybe Hadoop) has a dependency on The solution is to shade these classes when performing the assembly stage. Add the following to your build.sbt, changing the UNIQUE part as necessary. The standard convention (I think?) is to use your company prefix, e.g. UNIQUE becomes com.mycompany. Or you can just leave it as-is.
|
Hi there,
I'm trying to use lmdbjni with spark, scala and sbt. My code works well when I run it inside idea. The problem comes when I build a jar of my code with "sbt assembly". At execution time I get the following error java.lang.UnsatisfiedLinkError: org.fusesource.lmdbjni.JNI.init() . I do have lmdbjni and lmdbjni-linux64 installed.
The text was updated successfully, but these errors were encountered: