Community
Participate
Working Groups
I just downloaded the new M4 build, but cant fire it up. Error message: JVM Terminated. Exit code=1 C:\WINNT\system32\javaw.exe -cp C:\eclipse\eclipse-SDK-3.0M4-win32\eclipse\startup.jar org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash C:\eclipse\eclipse-SDK-3.0M4-win32\eclipse\eclipse.exe -showsplash 600
Please answer questions/follow instructions given in bug 38871.
I am using a java 1.4 version, appearently a beta, installed at its default location: C:\j2sdk1.4.0_01 C:\BP_HOME>java -version java version "1.4.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode) I have tried following the instructions at http://www.eclipse.org/eclipse/faq/eclipse-faq.html#users_3, forcing the VM location, it however gives produces a simular error: JVM Terminated. Exit code=1 c:\j2sdk1.4.0_01\bin\javaw.exe -cp C:\eclipse\eclipse-SDK-3.0M4-win32\eclipse\startup.jar org.eclipse.core.launcher.Main -os win32 -ws win32 -arch x86 -showsplash C:\eclipse\eclipse-SDK-3.0M4-win32\eclipse\eclipse.exe -showsplash 600 It is a new problem in the 3.0M4 build, I have used a number of other eclipse builds with this vm, including 2.1.1, 3.0M1, 3.0M2 and 3.0M3.
Eclipse fails to start for me on Sun JDK 1.4.0_04. Following are the related entries in my log file. Is this what you get in your log file (<workspace>/.metadata/.log)? Looks like a bug in the VM. Please try with a more recent VM (1.4.1 or 1.4.2). Moving to JDT/Core. Could you guys comment on this? Seems related to bug 43429. !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 Oct 14, 2003 09:23:17.419 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:299) at org.eclipse.core.launcher.Main.run(Main.java:765) at org.eclipse.core.launcher.Main.main(Main.java:599) Caused by: java.lang.reflect.InvocationTargetException at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:861) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) ... 7 more Caused by: java.lang.AbstractMethodError at org.eclipse.ui.internal.commands.CommandManager.readRegistry(CommandManager.java:763) at org.eclipse.ui.internal.commands.CommandManager.<init>(CommandManager.java:198) at org.eclipse.ui.internal.commands.CommandManager.getInstance(CommandManager.java:67) at org.eclipse.ui.internal.Workbench.initializeCommandsAndContexts(Workbench.java:1021) at org.eclipse.ui.internal.Workbench.init(Workbench.java:1710) at org.eclipse.ui.internal.Workbench.run(Workbench.java:2318) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858) ... 8 more
Really moving now...
Could this be related to the fact that you have a conflict with the xerces version on the classpath?
The line where the error occurs is not related at all to XML parsing, and I don't have Xerces in my boot classpath. This is the line in org.eclipse.ui.internal.commands.CommandManager that causes the AbstractMethodError: if (!this.definedCategoryIds.equals(definedCategoryIds)) { where both are SortedSets. Initially I thought that it could be a problem in the code generated by the Eclipse Java compiler. Then I found bug 43429 where a similar thing happens and Philippe says it is actually a VM bug. So, I just wanted to confirm this is a duplicate of that bug.
This indeed looks the same. Should give it a try on a different JRE (using 1.4.1 for instance).
Same here - tried to start with the default vm and jdk 1.3 and 1.4.0 eclipse.exe -vm c:\j2sdk1.4.0\bin\javaw.exe eclipse.exe -vm c:\jdk1.3\bin\javaw.exe I get the splash screen and then message box with VM terminated message. M3 worked fine
The failure with JDK 1.3 is a different issue (Eclipse requires a 1.4 VM). See bug 44814. The problem only happens with Sun JDK 1.4.0. Works fine with 1.4.1 or 1.4.2. The interesting thing is that the line that causes the problem in M4 was already there in M3 (and M3 works fine). Could any recent change in the compiler have something to do with that?
Problem resolved by using JDK 1.4.2 Thanks!
On j2sdk1.4.0_01 I don't even get a .log file. All I get is the error dialog described in the original error posting.
Closing as 1.4.0 VM bug *** This bug has been marked as a duplicate of 43429 ***
*** Bug 46014 has been marked as a duplicate of this bug. ***
