Hide Forgot
Title: Run the JBoss EAP Installation Program Describe the issue: On Linux and Windows the jvm architecture is associated with current jdk instance (cannot use -d32 switch on 64-bit jdk instance), however on Solaris and HP-UX user have to explicitly specify required architecture by -d32/-d64 switch. This could be problem on HP-UX as we support only 64-bit mode. Installer started by default 'java -jar <installer>' command wouldn't offer user to install native packs, as 32-bit HP-UX is not supported. User have to start installer by 'java -jar -d64 <iinstaller>' command so the native packs are correctly offer. Suggestions for improvement: We should mention the usage of -d32/-d64 switches in Installation guide.
FYI Taken from http://www.oracle.com/technetwork/java/hotspotfaq-138619.html ... The options -d32 and -d64 have been added to the Java launcher to specify whether the program is to be run in a 32 or 64-bit environment. On Solaris these correspond to the ILP32 and LP64 data models, respectively. Since Solaris has both a 32 and 64-bit J2SE implementation contained within the same installation of Java, you can specify either version. If neither -d32 nor -d64 is specified, the default is to run in a 32-bit environment. Other Java commands (javac, javadoc, etc.) will rarely need to be executed in a 64-bit environment. However, the -d32/-d64 options may be passed to these commands and then on to the Java launcher using the established -J prefix option (eg: -J-d64). All other platforms (Windows and Linux) contain separate 32 and 64-bit installation packages. If both packages are installed on a system, you select one or the other by adding the appropriate "bin" directory to your path. For consistency, the Java implementations on Linux accept the -d64 option.
Verified during eap-640-postGA-bulk4-docs check Revision 6.4.0-35