This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Adding Java arguments to .jvm files
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2008
08:00 AM
Adding Java arguments to .jvm files
Hi,
There are a few platforms where a 32-bit JVM is launched by default when you run a .sh installer. I want to launch a 64-bit JVM. On HP-UX for example, when I run the "java" command I would use the "-d64" switch on the command line to run it in 64-bit mode. How do I specify Java arguments such as the "-d64" switch inside a .jvm file? There doesn't seem to be any documentation on this.
Regards,
El Pibe
There are a few platforms where a 32-bit JVM is launched by default when you run a .sh installer. I want to launch a 64-bit JVM. On HP-UX for example, when I run the "java" command I would use the "-d64" switch on the command line to run it in 64-bit mode. How do I specify Java arguments such as the "-d64" switch inside a .jvm file? There doesn't seem to be any documentation on this.
Regards,
El Pibe
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 20, 2008
10:52 AM
If you are going to bundle a JVM you need two seperate launchers, one for Itanium and one for the 32 bit platform.
I'm not sure how you are creating your releases - are you using one Build Category or one for each platform? If you notice in the Distributions there are 3 different Lunchers for HP. If you want to use one launcher for HP and not use a bundled JVM then I guess you could just select the HPIA64 and select all the searches for JVM - there are 32 bit search routines under the ia64:
jvms/hpux_ia64 %
hp_hpux_14x_32bit.jvm
hp_hpux_14x_64bit.jvm
hp_hpux_15x_32bit.jvm
hp_hpux_15x_64bit.jvm
hpux1.4.2.02ia64.bin
Regards,
Tom
I'm not sure how you are creating your releases - are you using one Build Category or one for each platform? If you notice in the Distributions there are 3 different Lunchers for HP. If you want to use one launcher for HP and not use a bundled JVM then I guess you could just select the HPIA64 and select all the searches for JVM - there are 32 bit search routines under the ia64:
jvms/hpux_ia64 %
hp_hpux_14x_32bit.jvm
hp_hpux_14x_64bit.jvm
hp_hpux_15x_32bit.jvm
hp_hpux_15x_64bit.jvm
hpux1.4.2.02ia64.bin
Regards,
Tom
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2008
12:33 PM
Perhaps I did not explain the problem clearly. I am not bundling the JVM. I want to launch a 64-bit JVM on HP-UX. I am using the .jvm files to search for a pre-installed JVM. The problem I have is that on platforms like HP-UX and Solaris, when the installer finds a JVM, the default behaviour is to always invoke it in 32-bit mode. This is true even if you use the "hp_hpux_15x_64bit.jvm" file. This is the same when launching Java on the command line - you have to use the "-d64" switch to launch Java with the 64-bit libraries.
The default "hp_hpux_14x_64bit.jvm" file contains the line "REQ_JAVA_ARGS:-d64" and I would have thought this is what I needed, however it doesn't seem to do anything. On Solaris I have worked around the problem using "JVM_EXE: bin/sparcv9/java" inside the .jvm file but doing the equivalent on HP-UX brings up a missing library error.
The default "hp_hpux_14x_64bit.jvm" file contains the line "REQ_JAVA_ARGS:-d64" and I would have thought this is what I needed, however it doesn't seem to do anything. On Solaris I have worked around the problem using "JVM_EXE: bin/sparcv9/java" inside the .jvm file but doing the equivalent on HP-UX brings up a missing library error.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)