I downloaded the latest version of eclipse (3.5.SR2) and get m2eclipse installed on.
Instead of running on sun-jdk-6 (which is obsolete for the recent Ubuntu 10.04 alpha), I have eclipse running on open-jdk-6.
Everything was just fine. I can open my existing project and have them compiled as well as running tests.
However, with m2eclipse installed on, my eclipse will crash every time I start it.
If I stopped the m2eclipse plugin from contacting the central repo, then eclipse will continue to run normally.
The craziest point is that eclipse will exit immediately as soon as the contacting to central repo finish, but leave no track in the log.
What should I do right now?
Yeah, I was having the same problem. Was driving me crazy. (Ubuntu 10.04). I modified my eclipse.ini to be as follows (NOTE: I have /usr/lib/jvm/java-6-sun as a soft-link to /usr/lib/jvm/java-6-sun-1.6.0.20) - NOTE the "-vm" line and following line:
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-vm
/usr/lib/jvm/java-6-sun/bin/java
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.200.v20090519
-product
org.eclipse.epp.package.reporting.product
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx1024m
Now everything works great! Thanks all for the help!
confirming the exact same problem!
.. and the solution, using Sun JDK 1.6 Update 17 x64 eclipse runs fine now.
System:
Intel Core 2 Duo,
Ubuntu 10.04 x64
I created https://issues.sonatype.org/browse/MNGECLIPSE-2241 for this issue. As reported by running "eclipse -vm /usr/lib/jvm/java-6-sun/bin/java" instead.
Me too: running eclipse -vm /usr/lib/jvm/java-6-sun/bin/java once fixed the problem, and allowed Maven to update correctly. Since doing that, it seems that using openjdk is fine again.
Related
DevCenter 1.5.0 won't start, even though it was working a few days ago. I have already tried as suggested by the answer to this question : Datastax Devcenter 1.1 fail to start
However it didn't work for me. It did lead me to think it might be due to having updated to Eclipse Mars Yesterday, perhaps?
Any ideas would be great. Thanks in advance.
In response to the comments below I am running windows 7. Also I just realised that even though my JAVA_HOME is set correctly I am gettng this error when I run java -version:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\username>java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
Update : I fixed the java -version issue above by removing java.exe from C:/Windows/System32/ . But DevCenter is still not working.
OS: Windows 10 Pro
Dev Center - 1.6.0 (downloaded as zip. to run, we need to unzip and it's ready to go)
Today I faced a similar problem and was able to resolve by deleting/uninstalling the current Dev Center and re-installing. When you delete manually, make sure you delete the .devcenter folder. You will then have to reconfigure the connection(s) that you were using.
-Regards
This issue occurs on my computer. it's was resolved.
do you make sure setup python 27 and java sdk 8u ? if was set up and it's not running you can check previous version 1.5
When i start android device monitor in android studio "Java has started but returned exit code = 13" error with java path files is displayed.
I am using "android studio (beta)0.89"
I fixed this problem on my Windows 7 computer by installing the 64 bit version of Java 8. I did not have to uninstall or downgrade Java.
Be careful when downloading the Java installation. According to this FAQ, you will probably end up with 32 bit if you use the default installation.
Manually select the 'Windows Offline (64-bit)' version here, rather than letting the Java website choose for you.
This has happened to me just now after installing the latest Java version (v8) which for some reason only comes with 32-bit support while my PC is 64-bit.
I fixed the issue by uninstalling the version 8 of Java which automatically downgraded to Java 7 and it works fine.
I have been able to fix this issue by uninstalling the 32-bit Java 8 version I had, and then installing the latest 64-bit Java 8 version instead. (I didn't have to downgrade)
I think you are trying to open the wrong version of the monitor.exe it might have been changed during an upgrade. Under sdk/tools/lib there should be both the 32 and 64 bit versions under the "monitor-x86 or _64" folder. try either one if it works good. If you want to download the 64bit java version you must use a 64 bit browser. example in IExplorer 11 + you can change it back to 32 bit and back to 64 bit when needed. I did try the java upgrade before and was still getting the java error.
Install both 32 and 64 bit of Java 8. That fixed it for me.
Follow the path provided in the error pop-up. Add the java path in the eclipse.ini file located in the monitor folder in android studio.
Add : -vm
C:\Program Files\Java\jre7\bin\java.exe(Path to your current java file)
Before: -vmargs
If you are running win8.X just go to control panel and uninstall the java 8 version and after everything works fine.
I ran into this issue, even though I had the latest x64 build of the Java 8 JDK installed and set to the JAVA_HOME environment variable.
For me at least, the first line of the error popup shows that it is using Oracle's symlink at C:\ProgramData\Oracle\Java\javapath to find the correct location of javaw.exe. In my case, this was actually pointing to the x86 build of the same version of the JRE, which I also had installed for some reason.
I ended up cleaning house and uninstalling all versions of JRE/JDK, and then reinstalling the latest x64 JDK. This realigned the symlinks, and now it's running smoothly.
Most of the other answers should help resolve this same problem, but for diagnostic purposes if you do have the x64 version installed already, it will probably help to check C:\ProgramData\Oracle\Java\javapath.
[SOLUTION]
Go to following file in your android SDK
Sdk\tools\lib\monitor-x86_64\monitor.ini
and add following line, you might have to change the path to your java
-vm C:\Program Files\Java\jre7\bin\java.exe
just before "-vmargs "
Found solution:
Uninstall Java 8 Update (64-bit)
Install Java 7 Update 71 (64 bit)
I also downgraded JDK from 8 to 7, but it might be not required
here's my system specs;
Arch Linux x86_64,
Kernel: 3.6.10-1-ARCH,
Gnome 3.6.2,
xf86-video-nouveau 1.0.4-1,
jdk7-openjdk 7.u9_2.3.3-1,
jre7-openjdk 7.u9_2.3.3-1,
jre7-openjdk-headless 7.u9_2.3.3-1,
lib32-libjpeg-turbo 1.2.1-1, libjpeg-turbo 1.2.1-1, libjpeg6-turbo 1.2.1-1
libpng12 1.2.50-2,
net-tools 1.60.20120804git-2,
unzip 6.0-6.
Ok, so there's the list of requirements that are installed, version numbers as well. Upon launch, the loading/splash screen won't even show, and then nothing... it just dies out. I attempted to launch it "aptana -v" and no output in the shell. I have looked for any error logs in ~/ , but nothing is there.
Other steps I've done is to delete any configuration folders/files for eclipse and aptana-secure in ~/. Also did a clean uninstall of just Aptana (not the dependencies), reinstall. Same result.
Any suggestions?
It appears that there is a mix up in the downloads. 32-bit and 64-bit got switched. If you are on 32-bit download 64-bit and vice versa. Hopefully it will be fixed soon.
See issues below:
Aptana 64 bit version crashes on startup on 64bit Linux OS with 64bit Oracle 7 java
Linux Installer Aptana_Studio_3_Setup_Linux_x86_3.3.0.zip contains x64 bit version of the project
I downloaded the 32-bit eclipse for my 32-bit fedora 12. I extracted the tar.gz without any error. But when i click on the eclipse executable, i am getting the error:
"Failed to load the JNI shared library "/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/../lib/i386/client/libjvm.so"
"
I am not able to resolve this error. Please inform how to proceed.
Regards,
Go to your eclipse folder
Open eclipse.ini file and check if there is -vm option set properly
Else set -vm in one line followed by your jdk installed bin folder.
Hope this helps yo solve your problem.
I'd suggest avoiding OpenJDK, as Eclipse will keep complaining about it.
So, navigate to http://java.com/en/download/manual.jsp and download appropriate Sun's Java package (32 or 64 bit, depending on your current installation). As Fedora uses RPMs for package management, I advise to use that method.
Then, after installation, run java -version in terminal, you should get something like:
$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)
I am trying to run eclipse and encounter the errors. I am using Kubuntu as my OS and when I typed java -version in terminal I got 'java version "1.6.0_23"'. I have openJDK installed but I am not sure what can I do next. Any thoughts? Thanks.
ERROR:
JVM terminated. Exit code=13
/usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-os linux
-ws gtk
-arch x86
-showsplash
- launcher /home/lucky/Downloads/eclipse/eclipse
-name Eclipse
--launcher.library /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.2.R36x_v20101019_1345/eclipse_1310.so
-startup /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
-exitdata 5cf8058
-product org.eclipse.epp.package.php.product
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
-jar /home/lucky/Downloads/eclipse//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
My eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.2.R36x_v20101019_1345
-product
org.eclipse.epp.package.php.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
-Xmx384m
Looking at the paths in the error it seems that you are not using eclipse from the ubuntu repositories (that's fine imo).
Check if the jvm is 64 or 32 bit. java -version will tell you. If you find this is a 64-bit jvm then go back to eclipse.org and download a eclipse version for 64-bit. You have eclipse for a 32-bit jvm. See your error message where it says -arch x86
Try to start eclipse from a shell using the -vm parameter. On ubuntu you can find the installed jre/jdk's under /var/lib/jvm/. E.g.:
./eclipse -vm /var/lib/jvm/sun-java6-jdk/bin
You could add this parameter to your eclipse.ini file.
Helps?
This could be of interest as well: Eclipse starting error of JVM terminated. Exit code=13 after upgrading Ubuntu updates
I have found solution for errors 13 and 1 in following video:
Eclipse Error 13 and Error 1
Both errors are fixed by editing eclipse.ini in eclipse directory.
Error 13 is fixed by adding complete path to javaw. In my case it is:
-vm
c:\Program Files\Java\jdk1.8.0_45\bin\javaw.exe
Error 1 is caused by setting arguments for virtual machine before setting vm. itself.
This means two lines we just added must be before the
-vmargs
line.
Done.
Specify the JVM you want to use in your eclipse.ini file, as described in http://wiki.eclipse.org/Eclipse.ini
I'd recommend using the JDK from Oracle; I'm not sure the current state of compatibility between Eclipse and OpenJDK.
This might sound a little odd but I have stumbled upon the same problem (StS 3.2.2 on Juno 4.2.2 with Java 7 u25 both 64 bit on win7) and nothing seemed to work, then I moved my sts out of the directory I originally installed it (d:#sts\springsource\sts-3.2.0.RELEASE) to (d:\springsource\sts-3.2.0.RELEASE), and now it works.
I kept it in both places and if I want to start it from its original location it promptly crashes with exit code 13, if I start it from the new place it works just fine.
So it might be that eclipse does not like hash marks, or it was "too far away" from root and some of the files paths-es went beyond 256 char. (Nonetheless its quite odd the get exit code 13 since in my case it had nothing to do with non-matching versions)
I had the same error.
I got through with the following:
which java
It gave me :/usr/local/java/jre1.7.0_25/bin/java
I went to the folder where eclipse was located (~/Developer/adt-bundle-linux-x86_64-20140624/eclipse/ in my case )
cd ~/Developer/adt-bundle-linux-x86_64-20140624/eclipse/
Then
./eclipse -vm /usr/local/java/jre1.7.0_25/bin
You can make this permanent by editing the eclipse.ini file:
Right after OpenFile I inserted 2 lines containing:
-vm
/usr/local/java/jre1.7.0_25/bin/java
The second line being the output from the which java command.
Now Eclipse loads for me but it misbehaves, hopefully not related.
I had this issue on my windows 8.1 machine. All the suggestions didn't fix my issue.
I then thought about the root cause. I believed it was caused by degrading from JDK-9 to JDK-8. I recently uninstalled JDK-9.
I went and checked the Environment Variable-->Path and it contained another Java reference of "C:\ProgramData\Oracle\Java\javapath".
I simply removed this extra "C:\ProgramData\Oracle\Java\javapath" from Path(environment variable), and My Eclipse worked.
I hope this helps others.