I am not able to open the spring tool suite in the centos.
Following is the exception which is causing this problem.:
JVM terminated. Exit code=13
/opt/jdk1.7.0_60/bin/java
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dosgi.requiredJavaVersion=1.7
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m //plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-jar /home/kapil/Desktop/springsource/sts-3.4.0.RELEASE
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /home/kapil/Desktop/springsource/sts-3.4.0.RELEASE/STS
-name STS
--launcher.library /home/kapil/Desktop/springsource/sts-3.4.0.RELEASE//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130807-1835/eclipse_1506.so
-startup /home/kapil/Desktop/springsource/sts-3.4.0.RELEASE//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.overrideVmargs
-exitdata 30000d
-product org.springsource.sts.ide
-vm /opt/jdk1.7.0_60/bin/java
-vmargs
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dosgi.requiredJavaVersion=1.7
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m
-jar /home/kapil/Desktop/springsource/sts-3.4.0.RELEASE//plugins /org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
Here is the output of the java -version command :-
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) Server VM (build 24.60-b09, mixed mode)
And here is the output of the which java command :-
/usr/bin/java
Make sure that the JVM version (32/64 bit) you use matches the eclipse version (32/64 bit).Add this line in your sts.ini file and test again -vm /ur_java_home/bin/javaw.exe
First location to check is whether your JDK is 32 bit or 64 bit. Next, sheck your sts.ini configuration values. Trial and error will see you through.
I finally got this to work
Note that is on my system.
-vm
C:/Program Files/Java/jre1.8.0_144/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.551.v20171108-1834
-product
com.springsource.sts.ide
–launcher.defaultAction
openFile
–launcher.XXMaxPermSize
384M
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xmn128m
-Xms256m
-Xmx768m
-Xss4m
-XX:PermSize=128m
-XX:MaxPermSize=384m
-XX:CompileThreshold=1000
-XX:+CMSIncrementalPacing
-XX:+UnlockExperimentalVMOptions
-XX:+UseG1GC
-XX:+UseFastAccessorMethods
Related
I installed over Ubuntu GNU/Linux 16.04.2 VM the latest eclipse IDE for C/C++ via the eclipse oxygen provided via http://www.eclipse.org/.
After a complete Installation when I try to run the eclipse Application I get the following error:
JVM terminated. Exit code=1
/usr/lib/jvm/java-9-openjdk-amd64/bin/java
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
--add-modules=ALL-SYSTEM
-Declipse.p2.max.threads=10
-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
-jar /home/user/eclipse/cpp-oxygen/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /home/user/eclipse/cpp-oxygen/eclipse/eclipse
-name Eclipse
--launcher.library /home/user/.p2/pool/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.550.v20170928-1359/eclipse_1629.so
-startup /home/user/eclipse/cpp-oxygen/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.appendVmargs
-exitdata 3d800b
-product org.eclipse.epp.package.cpp.product
-vm /usr/lib/jvm/java-9-openjdk-amd64/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
--add-modules=ALL-SYSTEM
-Declipse.p2.max.threads=10
-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/
-jar /home/user/eclipse/cpp-oxygen/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
Do you have any idea why?
I had this same problem and have just managed to fix it.
The error message is saying that it is looking for Java version 1.8, but it can only find version 1.9.
First make sure you have java 1.8 installed.
If you open a terminal and enter the command RustyX suggested:
sudo update-alternatives --config java
you will be shown a lists of java versions on your machine and asked to select a version to be your default. Pick 1.8 and try opening eclipse again, it should work now.
I have come across a problem with my latest eclipse oxygen on Ubuntu 14.04 (installed within VMware). Each time after being launched for several minutes and operated on, it crashes.
This is the error message that always pops up:
JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /opt/eclipse//plugins/org.eclipse.epp.package.common_4.7.0.20170620-1800/splash.bmp
-launcher /opt/eclipse/eclipse
-name Eclipse
--launcher.library /opt/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.500.v20170531-1133/eclipse_1624.so
-startup /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.appendVmargs
-exitdata cc0022
-product org.eclipse.epp.package.cpp.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
There is no .log file in .metadata folder the first time it crashes in a freshly-created workspace.
By entering in terminal file /etc/alternatives/java /etc/alternatives/javac, the output is:
/etc/alternatives/java: symbolic link to `/usr/lib/jvm/java-8-oracle/jre/bin/java'
/etc/alternatives/javac: symbolic link to `/usr/lib/jvm/java-8-oracle/bin/javac'
and java -version yields
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
Also, in case it may be of any use, below is my eclipse.ini file:
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.500.v20170531-1133
-product
org.eclipse.epp.package.cpp.product
-showsplash
org.eclipse.epp.package.common
--launcher.defaultAction
openFile
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
I have tried a lot of methods online but none matches my case perfectly and none seems to be working.
My Eclipse was downloaded from the official site (the C/C++ package) and placed under /opt. Everything is 64-bit. I also tried deleting the eclipse package file and reinstall but failed many times with the same problem. (Not sure whether deleting the file means "uninstalling" it)
Hope someone could help! Much appreciated!
This question already has answers here:
Can't start Eclipse - Java was started but returned exit code=13
(44 answers)
Closed 8 years ago.
Both eclipse and jdk are 64 bit.
Environment variables:
classpath: C:\Program Files\Java\jdk1.7.0_45\jre\lib
path: C:\Program Files\Java\jdk1.7.0_45\jre\bin
I added the these lines to my eclipse.ini file:
-vm
C:\Program Files\Java\jre7\bin\javaw.exe
My java version details:
C:\Users\Owner>java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
My eclipse.ini file:
I have edited the required version from 1.5 to 1.7
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jre7\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms40m
The Error Details:
Java was started but returned exit code=13
C:\Program Files\Java\jre7\bin\javaw.exe
-Dosgi.requiredJavaVersion=1.7
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar
C:\ECLIPSE\ECLIPSE\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-os win32
-ws win32
-arch x86
-showsplash
-launcher C:\ECLIPSE\ECLIPSE\eclipse.exe
-name Eclipse
--launcher.library
C:\ECLIPSE\ECLIPSE\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.
v20120502\eclipse_1406.dll
-startup
C:\ECLIPSE\ECLIPSE\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.overrideVmargs
-exitdata 19b4_60
-product org.eclipse.epp.package.java.product
-vm C:\Program Files\Java\jre7\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-jar
C:\ECLIPSE\ECLIPSE\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
Please help. I have tried re-installing everything twice. Nothing has helped.
and it seems like the eclipse.ini file has been manupilated before
you have a 32 bit jvm, but your requirements are that of a 64 bit
use the x86 java.exe n check if it works by that i mean use the ProgramFilesx86 path
I am currently using openSuSE with XFCE and I installed Eclipse through YAST. Ecipse is version 3.4.0 and usually it crashes for no reason but I have been able to recreate the error when I write the the '.' in import java.io.*; and the 'err' in System.err.println();.This is the error message eclipse emits:
JVM terminated. Exit code=127
/usr/bin/java
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-jar /usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /usr/lib64/eclipse//plugins/org.eclipse.platform_4.3.0.v20130605-2000/splash.bmp
-launcher /usr/lib64/eclipse/eclipse
-name Eclipse
--launcher.library /usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130521-0416/eclipse_1506.so
-startup /usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.appendVmargs
-exitdata 1cd0022
-vm /usr/bin/java
-vmargs
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-jar /usr/lib64/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
java -version returns
java version "1.7.0_40"
OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-8.18.1-x86_64)
OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode)
You need to look at the .log file to resolve the problem. It is located in the workspace/.metadata/.log . It will tell you why it is crashing and will give you the stacktrace of the issue.
You might want to try adding
org.eclipse.swt.browser.DefaultType=mozilla
to eclipse.ini file.
When I try to run eclipse under Fedora core 13 x86_64, eclipse seems to run and then exit without an error.
My install consisted of downloading this file from the Eclipse Amazon mirror:
eclipse-jee-helios-linux-gtk.tar.gz
untarring it in my home dir, cd'ing into the reulsting eclipse dir and running the eclipse executable.
The executable seems to run and then exit without displaying so much as a splash screen.
Can anyone suggest what I am doing wrong?
See below for version details and a run of eclipse with the -debug flag.
Thanks for any suggestions.
[a1155344#minimi eclipse]$ cat //etc/issue
Fedora release 13 (Goddard)
Kernel \r on an \m (\l)
[a1155344#minimi eclipse]$ uname -a
Linux minimi 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64
x86_64 x86_64 GNU/Linux
[a1155344#minimi eclipse]$ cat eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.0.v20100503
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
[a1155344#minimi eclipse]$ java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
[a1155344#minimi eclipse]$ ./eclipse -debug
Start VM: /usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /home/a1155344/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-os linux
-ws gtk
-arch x86
-showsplash
-launcher /home/a1155344/eclipse/eclipse
-name Eclipse
--launcher.library /home/a1155344/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.0.v20100503/eclipse_1307.so
-startup /home/a1155344/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-exitdata c08023
-product org.eclipse.epp.package.jee.product
-debug
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
-jar /home/a1155344/eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
Install location:
file:/home/a1155344/eclipse/
Configuration file:
file:/home/a1155344/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/a1155344/eclipse/configuration/
Framework located:
file:/home/a1155344/eclipse/plugins/org.eclipse.osgi_3.6.0.v20100517.jar
Framework classpath:
file:/home/a1155344/eclipse/plugins/org.eclipse.osgi_3.6.0.v20100517.jar
Splash location:
/home/a1155344/eclipse/plugins/org.eclipse.platform_3.6.0.v201006080911/splash.bmp
Debug options:
file:/home/a1155344/eclipse/.options not found
Time to load bundles: 29
Starting application: 2773
[a1155344#minimi eclips
e]$
Make sure you are running the correct architecture with the correct JVM.
64bit Eclipse needs a 64bit JVM to run a 32bit Eclipse needs a 32bit JVM to run.
Also be certain to use the Sun JVM. Subtle errors occasionally occur with other JVM's.