Link to home
Start Free TrialLog in
Avatar of Daniel Wilson
Daniel WilsonFlag for United States of America

asked on

Eclipse (Scala configuration) fails to create JVM on Win7 64-bit

I am setting up a VM to begin working with Scala.  My machine runs Windows 7 64-bit.

I have installed Eclipse 64-bit as configured at scala-ide.org.  Actually, I just unzipped it into c:\program files\eclipse.

I then installed Java 1.7.  Since I was running 32-bit IE, the 32-bit version installed.  Running into trouble with that (Eclipse insisting it couldn't find a JVM) I installed Java 1.7, 64-bit.

So I have 64-bit Windows, Eclipse, and Java.  I added the 64-bit Java bin directory to my PATH variable.  I also put that path in the eclipse.ini file.
-vm
C:\Program Files\Java\jre7\bin

When I start Eclipse, it says:
Error: Could not create the java Virtual Machine
Error: A fatal exception has occurred. Program will exit.

I read that this is usually a memory constraint.  But Task Manager reports 2100 MB free.
Just in case, I changed
-Xmx1048m
 to
-Xmx512m

No better.

What am I overlooking?

Thanks!
Avatar of Sharon Seth
Sharon Seth
Flag of India image

what happens when you run java.exe from the command line?
Avatar of Daniel Wilson

ASKER

I've tried
java -version
and it tells me I have the 64-bit version of Java 7.something.
SOLUTION
Avatar of Sharon Seth
Sharon Seth
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No change, but this is noteworthy.

After the box that lists the 2 errors, a LONG message box comes up saying:
Java was started but returned exit code=1
c:\windows\system32\javaw.exe
-Xmx512m
-Xms100m
-XX:MaxPermSize=256m
-vm c:\program files\java\jre\bin\javaw.exe
etc.

Open in new window


So ... I think it's not using java.exe or javaw.exe where I tell it to, but in system32.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Specifying the EXE in the -VM path did not solve it, but led me to the solution.