64-bit Eclipse runtime prompts a solution for "Failed to load the JNI shared library \java\jre6\bin\client\jvm.dll"
Due to changes in the development environment, the 64-bit Juno 64-bit SP1 environment was replaced with the original Juno 32-bit. Results start Eclipse Error:
"Failed to load the JNI shared library" E:\2000\Java\JDK6\bin\. Jre\bin\client\jvm.dll "
Other environments use the default JDK 1.6.0_37 32 bits, default and configured in the default variable java_home, and the path is E:\2000\Java\JDK6.
So the newly installed JDK 1.6.0_37 64 bits, the path is E:\2000\Java\JDK64, start eeclipse again error, ditto.
To think about it, eclipse should start by looking for the JVM first from its own configuration, and then add two lines to the Eclipse.ini:
-vm
E:\2000\Java\JDK64\bin\javaw.exe
Still wrong, ditto. So simply put the system environment variable, Java_home set to: E:\2000\Java\JDK64. This time the normal boot, but the other system to use 32-bit time, and reported the same error. Looking at the Eclipse.ini carefully, the following items were added after openfile :
-vm
E:/2000/java/jdk64/bin/javaw.exe
And I was added at the end of the file, location error, so not effective. (Invite the Month Note: actually put the original two lines after OpenFile also can.) So, reset the java_home to: E:\2000\Java\JDK6
Try restarting eclipse with E:\2000\Java\eclipse\eclipse.exe-clean-nl en_US, resulting in an error:JVM terminated. Exit Code=-1
Take a closer look and consider possible memory parameter issues:
Will:
-vmargs
-dosgi.requiredjavaversion=1.5
-dhelp.lucene.tokenizer=standard
-xms40m
-xmx512m
Modified to:
-vmargs
-dosgi.requiredjavaversion=1.5
-dhelp.lucene.tokenizer=standard
-xms40m
-xmx256m
Reboot, finally normal.
After the normal start, and then change back to 512M, you can still start eclipse normally. It seems that eclipse has " wisely " memorized the correct configuration.
Author: Cnblogs invited the month
More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/Java/