No, both are 64-bit. Found a solution, and it's a bit of an odd one. I had to
have both JDK and JRE installed for this error to go away. Even though JDK
is referenced in JAVA_HOME, it needed JRE installed for some reason.
And what's also a bit confusing is that 'regular' Apache Ignite launched
from
What's crazy is that I just tried the same thing on another identical server
and getting the error again, even with c++ redistributable package
installed. Confirmed jmv dll is at the first path location below, and ignite
still works if launched from \bin folder.
Any suggestions ?
Here's the full er
On latest version of apache.ignite. Installed as Windows service on Win 2016.
Added this entry to AppSettings section in Apache.Ignite.exe.config:
If I launch apache.ignite.exe via command prompt, it reads the above config
correctly. If I launch from the same location as service, the config file
Installing 2010 MFC redistributable actually fixed the issue. Thought it was
not needed in the latest version, but I guess it still is.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi. I have the latest version of Ignite on Win 2016 x64. JDK v.12 x64 is
installed and referenced.
Running Ignite using \bin\ignite.bat works fine. I'm trying to have Ignite
launch as a service, but running \platforms\dotnet\bin\Apache.Ignite.exe
produces this error, jvm.dll error=DLL could not be
