> I think you did the right thing with the name of the file and directory, but > the content of jvm.cfg should be slightly different. > > For the Oracle Java 7 release this is correct because there's only a 64-bit > JDK. For a universal JDK, I think -client and -server should both be valid > choices.
Oracle Java 7 release support both -d32 and -d64 in command line but still report a 64bits VM java -d32 -version java version "1.7.0_04-ea" Java(TM) SE Runtime Environment (build 1.7.0_04-ea-b225) Java HotSpot(TM) 64-Bit Server VM (build 23.0-b09, mixed mode) OpenJDK 7 64bits didn't support -d32 by default (ie: in non universal mode) > # List of JVMs that can be used as an option to java, javac, etc. > # Order is important -- first in this list is the default JVM. > # NOTE that this both this file and its format are UNSUPPORTED and > # WILL GO AWAY in a future release. > -server KNOWN > -client KNOWN > > -hotspot ERROR > -classic WARN > -native ERROR > -green ERROR > > I apologize for just making random suggestions, but I'm not in a position to > test it out right now. I updated jvm.cfg under jre/lib/jvm.cfg and switching from -client IGNORE to -client KNOWN but didn't see any changes
