Error: Could not create the Java Virtual Machine

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Clean install UMS 1.1.1
2. Select 1536 for java heap size (1.5G on 12G machine)
3. Start UMS

What is the expected output? What do you see instead?
You would expect the app to load but you get an Java Virtual Machine Launcher 
error instead.

What version of the product are you using? On what operating system?
1.1.1 Win 7 x64, java 1.7.0_02-b13 installed

Please provide any additional information below.
Previous Subjunk /PMS builds run fine

Original issue reported on code.google.com by matthew....@gmail.com on 16 Jun 2012 at 5:22

Attachments:

• umserror.PNG

[GoogleCodeExporter]

You can fix it by using less memory

Original comment by subjunk on 18 Jun 2012 at 9:03

• Changed state: Invalid

[GoogleCodeExporter]

I'm having the same issue. How can I change the ammount of memory configured 
during install?

The weird thing is that if I specify the same ammouht of memory, or even more, 
using the -Xmx option of the bat file it does work ok!

Original comment by org...@gmail.com on 18 Jun 2012 at 11:52

[GoogleCodeExporter]

Maybe SharkHunter can help since he wrote that feature, I've Cc'd him on this 
issue

Original comment by subjunk on 18 Jun 2012 at 11:55

[GoogleCodeExporter]

I had java 32 bit installed and ums.exe was using it. I removed the 32 bit 
version and now it works ok!

Original comment by org...@gmail.com on 19 Jun 2012 at 12:04

[GoogleCodeExporter]

It was working with the bat because the bat uses the system default javaw. I 
guess the issue was really too much memory with my 32 bit 1.6 version of java.

Original comment by org...@gmail.com on 19 Jun 2012 at 12:06

[GoogleCodeExporter]

Interesting how did you deduce that it was using 32-bit java?  Also if the JVM 
setting is under 4GB why would that make a difference?  I mean obviously it 
did, but I'm at a loss.

Original comment by matthew....@gmail.com on 19 Jun 2012 at 12:06

[GoogleCodeExporter]

I uninstalled ums and installed it again. During the new installation I left 
the default configuration and it did start ok. Them I saw that it was using my 
32 bit java in the Traces tab.
I don't know if the program would ocurr with a recent 32 bits version of java. 
The version I had installed was an old 1.6 version.

Original comment by org...@gmail.com on 19 Jun 2012 at 12:18

[GoogleCodeExporter]

Oh.  Yeah mine worked fine when I reinstalled with the default value also.
I think though that there is certainly a 'valid' error here.

Original comment by matthew....@gmail.com on 19 Jun 2012 at 12:34

[GoogleCodeExporter]

This problem is what the heap feature is there to solve. The memory limit you 
set is how much heap mem the JVM should have. I've found out that the JVM 
somehow "allocates" (or at least check if it can get it or something) this 
amount at startup which means that if you have a lot of other programs running 
the amount of memory the JVM can get will be lower. This is tricky stuff and 
the only way is to try with various values. For example I had 4GB and said the 
JVM should use 1,5GB (if I used 768MB my web streams didn't work they skipped 
ahead). But if I used 1510MB it didn't start.

If you don't want to run the installer agian you can change the value in the 
registry. Start "regedit" and under "HKEY_CURRENT_USER\SOFTWARE\UMS" you'll 
find a property called "HeapMem" change that on to the value you need.

Original comment by bajen.hasse on 19 Jun 2012 at 6:47