Oxygen XML Forum

Hello,

I'm using oXygen XML Editor 9.2 on an Intel-based Mac running 10.5.3. The console posts this when I launch the editor:

5/29/08 11:08:09 AM [0x0-0x33033].ro.sync.exml.Oxygen[348] [JavaAppLauncher] A 64-bit JVM is available for 1.5.0

Does anyone have any information they can share about upgrading this JVM to take advantage of this hardware's 64-bit architecture?

Thanks,
Shannon
UVA Press

Hello,

You need a 64-bit Intel Mac OS 10.5 computer for running the Apple 64-bit Java virtual machine. If you already have a 64-bit processor and you start Oxygen by double clicking on the Oxygen icon then it should start with the 64-bit JVM if this JVM is installed because it is the preferred version of the JVM.

If it does not start with the 64-bit JVM then this JVM is not installed so you have to install the Java update for OS 10.5 from Apple.

If you start Oxygen by running the command

sh oxygenMac.sh

in a Terminal session you have to add the -d64 parameter to the java command before the "-Xdock:name=Oxygen" parameter at the end of the oxygenMac.sh script so that the 64-bit JVM is preferred.


Regards,
Sorin

Hi, Sorin,

Thanks for the response and helpful information.

I installed the Java update from Apple, rebooted, but console reports the same message.

I always launch oXygen using the icon I've placed in my dock.

Also, I edited oxygenMac.sh, but when I attempt to execute it, I get Java usage help as well as this error:

line 49: -Xdock:icon=Oxygen.app/Contents/Resources/Oxygen.icns: No such file or directory

I would prefer to use the 64-bit JVM, but I don't want to cause you any trouble

Thanks!
Shannon

Does your Mac computer have a 64 bit processor? You can run the 64-bit JVM only on a 64-bit processor.

Do you get the error about the Oxygen.icns file with the original file oxygenMac.sh that you had before adding the -d64 parameter? Adding the -d64 parameter should not generate that error. Does the file Oxygen.app/Contents/Resources/Oxygen.icns exist on your computer?


Regards,
Sorin

Dear Sorin,

Yes, this iMac has an Intel Core 2 Duo processor which is 64-bit (http://en.wikipedia.org/wiki/Core_Duo).

I downloaded oxygen.tar again from your site to restore the original oxygenMac.sh file. oXygen opens successfully now when I execute the script.

However, adding the -d64 parameter does result in that error.

java "-Xdock:name=Oxygen"\
-d64
-Xdock:icon=dist/oxygen/Oxygen.app/Contents/Resources/Oxygen.icns\
-Dcom.oxygenxml.editor.plugins.dir="$OXYGEN_HOME/plugins"\
-Xss650k\
-Xmx256m\
-cp "$CP" ro.sync.exml.Oxygen "$@"

sss4r:oxygen sss4r$ sh oxygenMac.sh
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)

where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available (implies -server, only for x86_64)
-client to select the "client" VM
-server to select the "server" VM
-jvm is a synonym for the "client" VM [deprecated]
-hotspot is a synonym for the "client" VM [deprecated]
The default VM is client.

-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A : separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
oxygenMac.sh: line 49: -Xdock:icon=dist/oxygen/Oxygen.app/Contents/Resources/Oxygen.icns: No such file or directory

Hello,

As I specified the first time you should add the -d64 aprameter before the "-Xdock:name=Oxygen" parameter. The reason is avoiding this kind of shell scripting errors. If you prefer to add the parameter on a new line you have to end the line with a \ character:
Regards,
Sorin

Sorin, thank you! I didn't ignore your instruction--when you stated "before" I thought you were referring to order, not syntax. At any rate, it works perfectly now when I launch using the script. That method creates a generic Java icon in my dock -- is there a way to use the 64-bit JVM by clicking the Oxygen.app icon? No biggie, just curious. Thanks again for your help!

It should start with the 64 bit JVM when you double click on the Oxygen icon too. The Info.plist file of Oxygen.app specifies the following preference list for the JVM: the 64 bit JVM for Intel Macs, the 32 bit JVM for Intel, the JVM for PowerPC. So if the JVM 1.5.0 for 64 bits is installed correctly on your Mac computer it should be the preferred JVM that is selected for running Oxygen 9.2. What JVM is used on your Mac computer?


Regards,
Sorin

Hi, Sorin,

It was a setting on this Mac -- I used Java Preferences.app to specify the preferred Java runtime to SE 6 (64-bit) or SE 5 (64-bit). Now when I load Oxygen.app, console no longer reports the message about a 64-bit JVM being available, so I'm assuming it is using it now. And now a "java -version" reports 64-bit, so everything is working well. Thanks for all your help!

Thanks,
Shannon