Skip to content
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

UnsatisfiedLinkError: no sqlite4java-linux-amd64-1.0.392 in java.library.path #68

Open
vdzhuvinov opened this issue Sep 26, 2017 · 13 comments

Comments

@vdzhuvinov
Copy link

Hi,
I would like to report an odd error. I setup pom.xml with the latest release. The plugin executes without any errors as configured, however, when trying to make a connection from within a test, an error complaining that an sqllite native .so cannot be found and loaded (on a Linux system) gets thrown:

SEVERE: [sqlite] SQLiteQueue[]: error running job queue
com.almworks.sqlite4java.SQLiteException: [-91] cannot load library: java.lang.UnsatisfiedLinkError: no sqlite4java-linux-amd64-1.0.392 in java.library.path
        at com.almworks.sqlite4java.SQLite.loadLibrary(SQLite.java:97)
        at com.almworks.sqlite4java.SQLiteConnection.open0(SQLiteConnection.java:1441)
        at com.almworks.sqlite4java.SQLiteConnection.open(SQLiteConnection.java:282)
        at com.almworks.sqlite4java.SQLiteConnection.open(SQLiteConnection.java:293)
        at com.almworks.sqlite4java.SQLiteQueue.openConnection(SQLiteQueue.java:464)
        at com.almworks.sqlite4java.SQLiteQueue.queueFunction(SQLiteQueue.java:641)
        at com.almworks.sqlite4java.SQLiteQueue.runQueue(SQLiteQueue.java:623)
        at com.almworks.sqlite4java.SQLiteQueue.access$000(SQLiteQueue.java:77)
        at com.almworks.sqlite4java.SQLiteQueue$1.run(SQLiteQueue.java:205)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.UnsatisfiedLinkError: no sqlite4java-linux-amd64-1.0.392 in java.library.path
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
        at java.lang.Runtime.loadLibrary0(Runtime.java:870)
        at java.lang.System.loadLibrary(System.java:1122)
        at com.almworks.sqlite4java.Internal.tryLoadFromSystemPath(Internal.java:352)
        at com.almworks.sqlite4java.Internal.loadLibraryX(Internal.java:124)
        at com.almworks.sqlite4java.SQLite.loadLibrary(SQLite.java:95)
        ... 9 more

Shouldn't java.library.path be set somewhere?

@0crat
Copy link

0crat commented Sep 26, 2017

@yegor256 please, pay attention to this issue

@yegor256
Copy link
Member

yegor256 commented Oct 4, 2017

@vdzhuvinov this is really weird. Can you share your pom.xml so that I can test it too?

@yegor256 yegor256 self-assigned this Oct 4, 2017
@0crat
Copy link

0crat commented Oct 4, 2017

Job gh:jcabi/jcabi-dynamodb-maven-plugin#68 assigned to @yegor256, please go ahead (policy).

@vdzhuvinov
Copy link
Author

@0crat
Copy link

0crat commented Nov 14, 2017

@yegor256 this job was assigned to you 8 days ago.
It will be taken away from you after 10 days from start (this is our policy).

@0crat
Copy link

0crat commented Nov 14, 2017

@yegor256 resigned from gh:jcabi/jcabi-dynamodb-maven-plugin#68, please stop working.

@0crat
Copy link

0crat commented Apr 12, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link

0crat commented Apr 17, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link

0crat commented Apr 22, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

@0crat
Copy link

0crat commented Apr 27, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link

0crat commented May 2, 2018

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@yegor256
Copy link
Member

yegor256 commented May 3, 2018

@0crat out

@0crat
Copy link

0crat commented May 3, 2018

@0crat out (here)

@yegor256 The job #68 is now out of scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants