Java Bootstack Options for Java Webstart

I have a problem running a Java RCP application through Java Webstart.

This works for others on the team, but not for me. (do you like such problems)

I believe the problem is that it is loading the 32-bit version of the application, not the 64-bit version.

When I look at the webstart.log file on my machine, I see the following.

!SESSION 2012-07-06 16:24:37.672 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_32 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB 

So, I think the problem is OS-win32, WS = win32.

My machine is Windows 7 64 bit.

Anyone have any ideas on how I should act?

+4
source share
1 answer

The bootloader constants seem to be misleading since when printing environment variables for a running JVM website:

OS: Windows 7 Arch: amd64

We tracked the problem down to the corresponding SWT jars for a non-downloadable user environment (to add fun to this RCP application deployed via webstart).

In the corresponding jnlp file, we had the following sections:

 <resources os="Windows" arch="x86"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_${org.eclipse.swt.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86_64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_${org.eclipse.swt.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86"> <jar href="plugins/org.eclipse.equinox.launcher.win32.win32.x86_${org.eclipse.equinox.launcher.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86_64"> <jar href="plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_${org.eclipse.equinox.launcher.win32.win32.x86.version}.jar"/> </resources> 

For most people, this was fine, since the 32-bit jre uploaded a resource for the x86 architecture, and everything was fine.

The problem on David's machine consisted of a 64-bit JVM, and it reports that the arch property was declared as amd64, not x86_64 (despite being an Intel processor).

Changing the resource section is as follows:

 <resources os="Windows" arch="x86"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_${org.eclipse.swt.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86_64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_${org.eclipse.swt.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="amd64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_${org.eclipse.swt.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86"> <jar href="plugins/org.eclipse.equinox.launcher.win32.win32.x86_${org.eclipse.equinox.launcher.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="x86_64"> <jar href="plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_${org.eclipse.equinox.launcher.win32.win32.x86.version}.jar"/> </resources> <resources os="Windows" arch="amd64"> <jar href="plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_${org.eclipse.equinox.launcher.win32.win32.x86.version}.jar"/> </resources> 
+3
source

All Articles