Open dimitrievgs opened 3 years ago
Ok, this one was solved with:
<properties>
<orientdb.version>3.1.11</orientdb.version> <!-- 3.0.37 -->
<jnr-ffi.version>2.2.4</jnr-ffi.version> <!-- Needed for orientdb since 3.1.X -->
</properties>
<dependencies>
<!-- https://mvnrepository.com/artifact/com.orientechnologies/orientdb-core -->
<dependency>
<groupId>com.orientechnologies</groupId>
<artifactId>orientdb-core</artifactId>
<version>${orientdb.version}</version>
</dependency>
<!-- https://mvnrepository.com/artifact/com.github.jnr/jnr-ffi -->
<dependency>
<groupId>com.github.jnr</groupId>
<artifactId>jnr-ffi</artifactId>
<version>${jnr-ffi.version}</version>
</dependency>
</dependencies>
OrientDB Version: 3.1.10 - 3.2.0
Java Version: OpenJDK 11
OS: Windows 10
Expected behavior
Trying to load latest java binding using
But get
error text
Jun 28, 2021 6:07:11 PM com.orientechnologies.common.log.OLogManager log INFO: Windows OS is detected, 262144 limit of open files will be set for the disk cache. Warning: Nashorn engine is planned to be removed from a future JDK release Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: 8523661312 B/8128 MB/7 GB of physical memory were detected on machine Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: Detected memory limit for current process is 8523661312 B/8128 MB/7 GB Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: JVM can use maximum 2034MB of heap memory Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: Because OrientDB is running outside a container 2g of memory will be left unallocated according to the setting 'memory.leftToOS' not taking into account heap memory Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: OrientDB auto-config DISKCACHE=4,046MB (heap=2,034MB os=8,128MB) Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: System is started under an effective user : `G` Jun 28, 2021 6:07:12 PM com.orientechnologies.common.log.OLogManager log INFO: Allocation of 61499 pages. Exception in Application start method java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at javafx.graphics/com.sun.javafx.application.LauncherImpl.launchApplicationWithArgs(LauncherImpl.java:464) at javafx.graphics/com.sun.javafx.application.LauncherImpl.launchApplication(LauncherImpl.java:363) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.base/sun.launcher.LauncherHelper$FXHelper.main(LauncherHelper.java:1051) Caused by: java.lang.RuntimeException: Exception in Application start method at javafx.graphics/com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:900) at javafx.graphics/com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:195) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.UnsatisfiedLinkError: java.lang.UnsatisfiedLinkError: could not locate stub library in jar file. Tried [jni/x86_64-Windows/jffi-1.2.dll, /jni/x86_64-Windows/jffi-1.2.dll] at jffi@1.2.19/com.kenai.jffi.internal.StubLoader.getStubLibraryStream(StubLoader.java:416) at jffi@1.2.19/com.kenai.jffi.internal.StubLoader.loadFromJar(StubLoader.java:359) at jffi@1.2.19/com.kenai.jffi.internal.StubLoader.load(StubLoader.java:262) at jffi@1.2.19/com.kenai.jffi.internal.StubLoader.Actual behavior
App doesn't start. It works (starts) with 3.0.37 version, but I want to check out if problem with updating properties only after restarting app persists in later versions (I will open another issue).
Steps to reproduce
Adds info to pom ^. Try to compile with code like:
<An SQL script to reproduce the problem or a JUnit test case will increase A LOT the chance to have a quick fix>