Is the server.exe compatible to start the objectdb server on Windows 64bit OS? Or 32bit only?
The problem is that it cannot start because it cannot find the jvm on the 64bit install
Java 7 is correctly installed with JAVA_HOME and JRE_HOME set.
The temporary workaround was to create a .bat file with the following command:
"C:\Program Files\Java\jdk1.7.0\bin\java" -server -Xms16M -Xmx256M -cp "objectdb.jar" com.objectdb.Server start
The OS is Windows Server 2008 R2 64bit
Have you tested server.exe on this environment?
see attached screen prints
It seems that explorer.exe and server.exe try to locate a win32 JVM (also on Windows 64) and if only a win64 JVM is available - they fail. Your workaround is good. You may also try installing win32 JVM in addition to the win64 JVM.
This will be fixed in one of the next builds. Thank you for your report.
I just tried this new version but it doesnt work for me. I have Windows 64bit with JAVA as you can see below. The version objectdb-2.3.4_02.zip works fine, but the new one objectdb-2.3.4_03.zip claims that JVM cannot be found when running server or explorer.
C:\>java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
Starting build 2.3.4_03 explorer.exe and server.exe are based on winrun4j.
Could you please write the exact error message? Which operating system do you use?
In addition, according to winrun4j documentation you may specify the path to the JVM in explorer.ini and server.ini files (in the directory of explorer.exe and server.exe), where each file has a single text line:
vm.location=C:\Program Files\Java\jdk1.6.0_29\jre\bin\server\jvm.dll
Notice that the specified path is to the jvm.dll file. Please try it.
Build 2.3.4_04 includes both:
Please try again server.exe and explorer.exe. They have been tested successfully on Windows 7 Pro 64. But if they still do not work - you will have to use the old server_.exe and explorer_.exe until the source of the problem is found.