java.lang.UnsatisfiedLinkError

no oojava in java.library.path


Samebug tips1

This happens sometimes when Android fails to load the necessary libraries when you install an app. Try reinstalling it or telling your client to reinstall it, as it seems to correctly install the libraries and fixes the problem.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.


Solutions on the web4571

Solution icon of oraclecommunity
no oojava in java.library.path

Solution icon of visual-paradigm
via Visual-paradigm by Dima, 1 month ago
no I1 in java.library.path :

Solution icon of coderanch
via Coderanch by Nandan Jain, 8 months ago
no jaas_nt in java.library.path

Solution icon of coderanch
via Coderanch by Garandi Garandi, 1 year ago
no ibmsynth in java.library.path

Solution icon of coderanch
no J3D in java.library.path

Solution icon of coderanch
via Coderanch by Sean Ansari, 1 year ago
no HelloJNI.dll in java.library.path

Solution icon of coderanch
no wlntio in java.library.path

Solution icon of bugzilla
via Eclipse Bugzilla by jared_burns, 1 year ago
no win32refresh in java.library.path

Solution icon of bugzilla
via http://bugs.gentoo.org/ by cjosephson, 7 months ago
no javagtk in java.library.path

Solution icon of github
via GitHub by robouden
, 1 year ago
no rxtxSerial in java.library.path

Stack trace

  • java.lang.UnsatisfiedLinkError: no oojava in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312) at java.lang.Runtime.loadLibrary0(Runtime.java:749) at java.lang.System.loadLibrary(System.java:820) at com.objy.pm.Binding.<clinit>(Binding.java:81) at com.objy.pm.ConnectionPersistor.<init>(ConnectionPersistor.java:76) at com.objy.pm.Access.new_ConnectionPersistor(Access.java:86) at com.objy.db.app.Connection.open(Connection.java:277) at com.carescience.db.objectivity.DatabaseServicesObjy.initializeDbConnection(DatabaseServicesObjy.java:347) at com.carescience.db.objectivity.DatabaseServicesObjy.<init>(DatabaseServicesObjy.java:98) at com.carescience.db.objectivity.DatabaseServicesObjy.getInstance(DatabaseServicesObjy.java:153) at com.carescience.db.DatabaseServicesFactory.getInstance(DatabaseServicesFactory.java:37) at com.carescience.cde.pids.IdentityServiceImpl.<init>(IdentityServiceImpl.java:58) at com.carescience.cde.pids.IdentityServiceImpl.<clinit>(IdentityServiceImpl.java:44) at com.carescience.cde.pids.IdentityServiceFactory.getInstance(IdentityServiceFactory.java:31) at com.carescience.cde.plist.PatientListMediatorImpl.<init>(PatientListMediatorImpl.java:32) at com.carescience.cde.ui.PatientListWebImpl.getMediator(PatientListWebImpl.java:39) at com.carescience.cde.ui.PatientListWebImpl.getLists(PatientListWebImpl.java:68) at jsp_servlet._patientsearch._jspService(_patientsearch.java:276) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:302) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 week ago
4 times, 2 months ago
Samebug visitor profile picture
Unknown user
Once, 2 months ago
2 times, 2 months ago
Samebug visitor profile picture
Unknown user
Once, 3 months ago
277 more bugmates