score:305

Accepted answer

the error message points to a problem with your java version. do you have a jdk installed?

try adding the following (noting the new line):

/!\ make sure, that the -vm option occurs before the -vmargs command. everything after -vmargs is passed directly to the jvm.

-vm 
c:/wherever/java/jdk1.6.0_21/jre/bin/server/jvm.dll
-vmargs... 

...to your eclipse.ini file, pointing to the jdk you want to use, and check that the required java version is at least as new as your jdk. this is the path for a windows system. more on paths can be found here (scroll down).

if you don't know where the eclipse.ini file is: regularly it is in the folder of your eclipse.exe.

edit2: @kadolakatt: the reason why installing the latest java version worked for you is because eclipse checks the standard path for a jvm if it doesn't find a -vm entry (see here). however i'd not recommend that, since you might be wrong guessing the jvm used. if you update java (automatically?) you might run into problems in your eclipse wondering what you might have changed. better set it to a specific folder in your eclipse.ini to be certain.

score:-4

if it says c:/program files/java/jre/bin/server/jvm.dll not found then copy the jre from jdk folder and paste it outside the jdk folder . and then try again...

score:0

just to add here...
for the guys those who still couldn't start eclipse due same error, please check eclipse.ini file again and see have you forgot to put m after memory size. for example:

-xmx1024
or
-xmx1024mb
or
-xmx1024 m
or
-xmx1024 mb
or
-xmx1024mb

are incorrect, it should be -xmx1024m. i have been trying different ideas from sof and from other forums, and in this cut/paste i forgot that i missed m (such a little thing to miss), so i thought i should share. if it works for some of you please up-vote.

score:0

i had this issue recently, but i hadn't changed any java or updated the java version, may be this issue happened because of crash shutdown of the system.

and after reading a couple of answers here i decided to change the java version from 1.6 to 1.7 in the eclipse.ini file.

-vmargs
-dosgi.requiredjavaversion=1.6  

after this change the eclipse started well and it worked. since i didnt had changed anything i decided to change it back to 1.6 to what it was originally.

then i started eclipse and guess what it worked. so looks like in my case just touching/modifiying the eclipse.ini file worked.

i hope this answer is helpful to somebody.

score:0

if none of the solutions works, please check if you have more than one version of java installed on your machine. please keep only one version which you prefer and everything should work fine.

score:0

none of the above answers helped for me. i discovered that, in general, an error like that could mean that your eclipse.ini has an invalid entry. so, all the above answers could be correct, depending on your particular case. in my case, it turned out i added a locale argument with a typo in it.

score:0

i tried to change the path in the parameter -vm, but it did not help. then i deleted the parameter -vm and -vmargs from the eclipse.ini. it worked for me

score:0

please check your computer and if java jre not install download and install it.

if install please check is it 32 bit or 64 bit as per your operating system

to check for 32 or 64-bit jvm, run:

$ java -d64 -version

$ java -d32 -version

error: this java instance does not support a x-bit jvm. please install the desired version.

score:0

my path of -javaagent argument was having spacial characters like '&'. i placed the lambok jar in different place and gave the path to that place. it worked for me.

previously it was

-javaagent:c:\software & tool\lambok.jar

i changed it to

-javaagent:c:\labmok\lambok.jar

score:0

  1. open the eclipse installation folder on windows machine

  2. find the eclipse.ini

  3. open the eclipse.ini file and add the below two lines before -vmargs

    -vm 
    c:\users\ishaqkhan\jdk1.8.0_173\bin\javaw.exe
    

score:0

this work for me in eclipse js and eclipse php:

 -vm
 c:/java/jdk-11.0.1/bin/javaw.exe
 --launcher.appendvmargs
 -vmargs

score:0

i had a similar issue. i opened my eclipse.ini file and noticed that i configured at the end some lines for the lombok library in the past. the path to my lombok jar file was no more valid. after correcting it, my eclipse was working like a charm again. in conclusion, my piece of advice would be to verify that all the paths configured in this file are valid.

eclipse.ini :

-...
-javaagent:c:\some\path\to\lombok.jar
-xbootclasspath/a:c:\some\path\to\lombok.jar

score:0

java path could be incorrect

trying above solution didn't help me. so i checked java --version on command prompt, which gave virtualization conflict. it seemed installation of virtualization software on system had messed up environment variables.

hence i checked java_home which was on correct path, then checked system variable path which had correct java bin path as well, so removed 'c:\program files (x86)\common files\oracle\java\javapath' and checked java --version on command prompt again, which gave correct value and also fixed above issue of eclipse start.

score:0

on windows 10, removing

-xstartonfirstthread

from the eclipse.ini fixed the issue for me

score:1

directly changing eclipse file is not a good idea, no matter facet or ini, unless it could be changed in eclipse. had the same problem, with jdk1.8 installed. change it to jdk 1.7.enter image description here

besides, according to https://wiki.eclipse.org/eclipse/installation, both luna and mars need 1.7. so just ensure you have it installed.

score:1

1 ) open the springtoolsuite4.ini file.
2 ) search for the openfile.
3 ) provide the jvm.dll file location in springtoolsuite4.ini
4 ) note : provide the new line between -vm and your jvm.dll file location path.as shown below.

openfile
-vm 
c:\program files\java\jre8\bin\server\jvm.dll
-vmargs
-dosgi.requiredjavaversion=1.8
-xms256m

enter image description here

score:1

i had java run time environment and java sdk both on my machine. i removed java run time environment and it resolved my error. earlier this error, i was using elipse with java sdk only and later had installed jre specifically for one need.

score:2

this can be resolved by adding the following line to the eclipse.ini file -xx:-usecompressedoops

score:2

i had the same issue which was caused due to crash shutdown of my windows 10. earlier in the path i had oracle path ie the path inserted by oracle at the time of installation of jdk. i removed it and changed the path to the jdk location. this solved the problem.

score:2

mine is a 64 bit system with 64bit java installation. what worked for me was the following:

  1. goto the eclipse installation directory
  2. right click the eclipse icon and click "send to desktop as shortcut"
  3. then right click on the shortcut icon in the desktop and then > properties > shortcut tab
  4. in the target field point it to the correct java 64 bit installations home path using the vm argument with the java_home path enclosed in quotes like so :

    d:\scala_eclipse\eclipse.exe -vm "c:\program files\java\jdk1.8.0_11"

    scala eclipse shortcut icon

this almost always solves all my eclipse (scala eclipse as well) related problems. as mentioned in the answer , please make sure you are using the right combination of eclipse and java

score:2

if you have java 8 installed it might be related to the following issue: https://support.oracle.com/knowledge/middleware/2412304_1.html

simply removing/renaming the "c:\program files (x86)\common files\oracle\java\javapath" worked for me.

score:3

i too faced the similar issue , not solved after adding the command in eclipse.ini file. my root cause is different. i was experimenting on sequence diagrams using objectaid. this is throwing an exception and disturbed my workspace. you may have different issue when working on new plugins. better you check the log file located in your project work-space c:\path\to\workspace\.metadata\.log

score:4

i had same issue in my windows 7, 64-bit machine. then i downloaded and installed 64 bit jdk for java(which includes jre). this solved the issue.

score:5

i've encountered similar problems. the reason is that the path to my eclipse includes chinese characters. once those characters are deleted, the problem is solved. please check if there are characters other than english in your path.

score:6

adding -vm parameters works for me.

-vm 
c:\program files\java\jdk1.7.0_45\jre\bin\server\jvm.dll

score:6

for those of you who tried all the above answers without any success, try lowering your -xms value. i am required to support an older eclipse (weblogic eclipse 10.3.6) - i had the following .ini on my windows 7 machine and my windows server 2008 r2 enterprise vm (the java version below points to a 32-bit java) that had worked and were working perfectly, respectively.

-vm
c:/java/java7/jdk1.7.0_79/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20120522-1813
-showsplash
org.eclipse.platform
--launcher.defaultaction
openfile
-vmargs
-xms1024m
-xmx1024m
-xx:maxpermsize=256m
-dsun.lang.classloader.allowarraysyntax=true
-dweblogic.home=c:/oracle/middleware/wlserver_10.3

so a 32-bit java for a 32-bit eclipse, but still exit code 1. based on all answers i had seen here, and the only change being a new laptop with windows 10, the only possible explanation was that the new os and the eclipse were disagreeing on something. so i started playing around with each of the values, and it worked when i lowered both xms and xmx to 512m. i have a hunch that possibly the new windows os is preventing a higher initial heap size based on some run condition (the higher -xms does work on windows 10 on all other similar devices i came across) - so any other explanation is welcome. meanwhile following is the only value i tweaked to successfully launch eclipse.

-xms512m 

score:7

working combinations of os, jdk and eclipse bitness.

  • 32-bit os , 32-bit jdk , 32-bit eclipse (32-bit only)
  • 64-bit os , 32-bit jdk , 32-bit eclipse
  • 64-bit os , 64-bit jdk , 64bit eclipse (64-bit only)

kindly use 1 of the above combinations.

score:12

it can be like this as well:

-vm 
c:\program files\java\jre6\bin\server\jvm.dll

score:48

i received this error out of the blue. eclipse stopped working even though i made no config changes and did not install any new jdk's.

here was my eclipse.ini file :

--clean
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.jee.product
--launcher.defaultaction
openfile
--launcher.xxmaxpermsize
256m
-showsplash
org.eclipse.platform
--launcher.xxmaxpermsize
256m
--launcher.defaultaction
openfile
-vm
c:/program files (x86)/java/jre7/bin/javaw.exe
--launcher.appendvmargs
-vmargs
-dosgi.requiredjavaversion=1.6
-xms40m
-xmx1024m

to get eclipse to start successfully i removed

    -vmargs
    -dosgi.requiredjavaversion=1.6
    -vm 
c:/program files (x86)/java/jre7/bin/javaw.exe

so here is my updated file :

--clean
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.jee.product
--launcher.defaultaction
openfile
--launcher.xxmaxpermsize
256m
-showsplash
org.eclipse.platform
--launcher.xxmaxpermsize
256m
--launcher.defaultaction
openfile
-xms40m
-xmx1024m

i have no idea why removing osgi.requiredjavaversion=1.6 fixed this as my jvm version is 1.6. from the doc http://help.eclipse.org/indigo/index.jsp?topic=%2forg.eclipse.platform.doc.isv%2freference%2fmisc%2fruntime-options.html

osgi.requiredjavaversion
the minimum java version that is required to launch eclipse. the default value is "1.4.1".

i think my java version was set correctly. anyway eclipse starts and runs for me now......


Related Query

More Query from same tag