| JVM terminated. Exit code=-1 [message #260843] |
Sat, 12 July 2008 01:03  |
Eclipse User |
|
|
|
Originally posted by: srgsoroka.gmail.com
I try to run Eclipse (eclipse-jee-ganymede-win32.zip).
But always receive error:
---------------------------
Eclipse
---------------------------
JVM terminated. Exit code=-1
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256M
-Djava.class.path=C:\Eclipse\plugins\org.eclipse.equinox.lau ncher_1.0.100.v20080509-1800.jar
-os win32
-ws win32
-arch x86
-showsplash
C:\Eclipse\\plugins\org.eclipse.platform_3.3.100.v2008061720 00\splash.bmp
-launcher C:\Eclipse\eclipse.exe
-name Eclipse
--launcher.library
C:\Eclipse\plugins\org.eclipse.equinox.launcher.win32.win32. x86_1.0.100.v20080509-1800\eclipse_1114.dll
-startup
C:\Eclipse\plugins\org.eclipse.equinox.launcher_1.0.100.v200 80509-1800.jar
-vm C:\Sun\SDK\jdk\jre\bin\client\jvm.dll
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256M
-Djava.class.path=C:\Eclipse\plugins\org.eclipse.equinox.lau ncher_1.0.100.v20080509-1800.jar
---------------------------
OK
---------------------------
Version of java:
C:\Documents and Settings\Administrator>java -version
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode)
C:\Documents and Settings\Administrator>
Please help me, eclipse-SDK-3.4-win32.zip and
eclipse-java-ganymede-win32.zip
running well.
|
|
|
|
|
|
| Re: JVM terminated. Exit code=-1 [message #261027 is a reply to message #260885] |
Mon, 14 July 2008 10:20  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Dimitrios Kolovos wrote:
> I had the same problem with a Ganymede release (the modeling release
> with the latest JDK - _07) and managed to overcome it by clearing the
> contents of the eclipse.ini file (further investigation showed that it
> was actually the -framework line and below that were causing this for
> some reason). Now I'm encountering random OutOfMemory errors but that is
> another story...
No, its not another story; it is most likely directly related. If you
remove everything after the -framework line, you've removed the args to
the JVM that tell it how much heap space to allocate. The default JVM
heap sizes are probably not enough to run Eclipse successfully, so you
need those settings.
You may have also removed the -vm param and its value, which would be
telling Eclipse specifically which JVM to run on. This is also a
mistake, as you never know what the system JVM is, especially since some
software is known to change it without your knowledge.
There was a thread last week about a JVM bug that led to hard crashes
like this. Can you try Java 5 or an earlier version of Java 6?
Eric
> Walter Harley wrote:
>> "Sergio" <srgsoroka@gmail.com> wrote in message
>> news:08bef6a9c6a599ec1bd0633c748f5f02$1@www.eclipse.org...
>>> I try to run Eclipse (eclipse-jee-ganymede-win32.zip).
>>> [...]
>>> Please help me, eclipse-SDK-3.4-win32.zip and
>>> eclipse-java-ganymede-win32.zip
>>> running well.
>>
>> If you had previously tried those other versions, and then tried
>> unpacking eclipse-jee-ganymede, did you clean out or delete the
>> directory first, or did you install on top of an existing Eclipse?
>> Installing on top of existing files won't always work well.
>>
>> Have you tried starting with eclipse-SDK-3.4-win32 and then upgrading
>> using Help -> Software Updates? You should be able to add the
>> packages you need that way, rather than by reinstalling. If you add a
>> feature at a time, that might also provide some hints about what
>> feature it is that is causing the failure.
>>
|
|
|
| Re: JVM terminated. Exit code=-1 [message #261355 is a reply to message #261027] |
Thu, 17 July 2008 07:02 |
| Eclipse User |
|
|
|
Hi Eric,
Thanks for your reply. My 3.3 installation (to which I've eventually
reverted) seems to be doing fine with all JVMs I've had so far (Java 5
or 6) but 3.4 has failed both with 1.6.0_04 and 1.6.0_07 (latest). I
find it hard to attribute this to a de-facto incompatibility between
those two versions of JVM and 3.4 as in this case I suspect that the
newsgroups would have been flooded with questions/complaints shortly
after the release of Ganymede.
Re the thread you mentioned, I'm always using winrar for unzipping so
this shouldn't be the source of my problem.
In any case, if there are known incompatibilities between particular
versions of Eclipse and JVMs wouldn't it be a good idea to have a wiki
page where this is reported?
Cheers,
Dimitrios
Eric Rizzo wrote:
> Dimitrios Kolovos wrote:
>> I had the same problem with a Ganymede release (the modeling release
>> with the latest JDK - _07) and managed to overcome it by clearing the
>> contents of the eclipse.ini file (further investigation showed that it
>> was actually the -framework line and below that were causing this for
>> some reason). Now I'm encountering random OutOfMemory errors but that
>> is another story...
>
> No, its not another story; it is most likely directly related. If you
> remove everything after the -framework line, you've removed the args to
> the JVM that tell it how much heap space to allocate. The default JVM
> heap sizes are probably not enough to run Eclipse successfully, so you
> need those settings.
> You may have also removed the -vm param and its value, which would be
> telling Eclipse specifically which JVM to run on. This is also a
> mistake, as you never know what the system JVM is, especially since some
> software is known to change it without your knowledge.
>
> There was a thread last week about a JVM bug that led to hard crashes
> like this. Can you try Java 5 or an earlier version of Java 6?
>
> Eric
>
>
>> Walter Harley wrote:
>>> "Sergio" <srgsoroka@gmail.com> wrote in message
>>> news:08bef6a9c6a599ec1bd0633c748f5f02$1@www.eclipse.org...
>>>> I try to run Eclipse (eclipse-jee-ganymede-win32.zip).
>>>> [...]
>>>> Please help me, eclipse-SDK-3.4-win32.zip and
>>>> eclipse-java-ganymede-win32.zip
>>>> running well.
>>>
>>> If you had previously tried those other versions, and then tried
>>> unpacking eclipse-jee-ganymede, did you clean out or delete the
>>> directory first, or did you install on top of an existing Eclipse?
>>> Installing on top of existing files won't always work well.
>>>
>>> Have you tried starting with eclipse-SDK-3.4-win32 and then upgrading
>>> using Help -> Software Updates? You should be able to add the
>>> packages you need that way, rather than by reinstalling. If you add
>>> a feature at a time, that might also provide some hints about what
>>> feature it is that is causing the failure.
>>>
|
|
|
|
Powered by
FUDForum. Page generated in 0.11351 seconds
Home