Created attachment 1118532 [details] Screenshot of the error Description of problem: When Installing BRMS/BPMS on specific OS/JDK combinations there is a failure on step "Deploy business-central.war" See the thrown exception in attachments. Version-Release number of selected component (if applicable): Combinations: Windows8.1/oracle-jdk1.8 (32bit JVM) Windows Server 2008/oracle-jdk-1.7(64bit JVM) How reproducible: always Steps to Reproduce: 1. Run Installer with OS/Jdk mentioned above 2. Use default settings 3. Process the installation Actual results: Exception is thrown and Installer fails the installation. Expected results: No exception is thrown and Installer succeeds. Additional info: Also I can't see anything in log and since it fails the installation it should be logged.
I believe that it is not necessary a bug, you can change the Xms and Xmx values: java -jar -Xms1024m -Xmx1024m brms-installer.jar Did you try this? IF you use this and look at Jconsole: Current heap size: 63,753 kbytes Maximum heap size: 1,005,056 kbytes Committed memory: 1,005,056 kbytes VM arguments: -Xms1024m -Xmx1024m Class path: /home/fspolti/Downloads/jboss-bpmsuite-6.2.0.GA-installer.jar Library path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib Boot class path: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-15.b17.fc23.x86_64/jre/classes
Hi Spolti, yes I have tried to change -Xms and -Xmx, but the results were the same. It is because Installer uses another jars to perform some operations and this error isn't caused in Installer's process but in a process invoked by Installer itself.
This, as we found out is not Installer bug, but the scenario when using 32bit JVM and 64bit OS. When this error occurs it should still be logged. I am degrading the severity since this BZ is now only about logging this error when occured.
The error will prevent installation, and in fact will prevent the domain mode of BxMS from running at all on the target machine. In this case, should we abort domain configuration in the installer and log the reason? If so this can be fixed early next week.
Verified with 6.3.0.ER3.