Skip to Main Content

Java HotSpot Virtual Machine

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

"Could not create the Java virtual machine." when max-heap-size is > 926Mb

801670Sep 29 2010 — edited Oct 1 2010
We received "Could not create the Java virtual machine." when the max-heap-size provided exceeded 926 Mb in XP PC. We found the below mentioned link which confirms that this is a bug

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6945136

But the problem is that the issue does not get recreated in all the XP PCs. Increasing the max heap size to greater than 926 works fine in some XP PCs.
Could there be any configuration related issues for this problem...

Comments

The bug is specific to Java Web Start (JWS).

Are you stating that using only JWS that on some machines it has the lower maximum and others that it doesn't?
And that all of those machines are running exactly the same version of java?
801670 Sep 30 2010 — edited on Sep 30 2010
Thanks for the reply.

All the machines have the same version of jre (1.6_19). In some PCs the jvm works fine even when max-heap-sixe > 926 Mb whereas in other PCs it shows the mentioned error.

The OS in all the machines is Windows XP 32 bit.

Edited by: crazybugs on Sep 30, 2010 1:28 AM
crazybugs wrote:
Thanks for the reply.

All the machines have the same version of jre (1.6_19). In some PCs the jvm works fine even when max-heap-sixe > 926 Mb whereas in other PCs it shows the mentioned error.

The OS in all the machines is Windows XP 32 bit.
And all of the applications use JWS exclusively? There is no other option?
801670 Oct 1 2010
There is only 1 application that uses JWS exclusively.. This application starts properly in some PCs whereas in others it throws "Could not create the Java virtual machine." error.

The max-heap-size is > 926Mb in all these cases.
I suggest you verify what versions are running - explicitly.
796440 Oct 1 2010
If you can't find any difference in your java versions or overall runtime configurations, it's quite possible that the bug doesn't have the complete picture--it might be more subtle than the conditions described. Maybe it works with certain versions of certain lower level DLLs. Maybe it has some dependency on which services are running. Maybe the order in which certain components got installed put one version of something vs. another further ahead in a CLASSPATH, LD_LIBRARY_PATH, etc. variable.

Or maybe it's as simple as you're not running the version of Java you think you are on all those boxes, as jschell suggests.

Regardless of the reason why it happens to work on some configurations, you found that it fails on some, and that failure is in fact a known bug. So it shouldn't surprise you that it fails at least sometimes, and the fact that it works sometimes has been rendered irrelevant. Unless you're doing research into the specific cause of this issue.
1 - 6
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 29 2010
Added on Sep 29 2010
6 comments
3,607 views