Description of problem: ====================== - Even if a JVM setting (like "Test") is created inside the "host.xml" as following the HAL console does not allow this JVM settings to be assigned to a server from console without altering the Heap settings. {code} <jvms> <jvm name="default"> <heap size="64m" max-size="256m"/> <permgen size="256m" max-size="256m"/> <jvm-options> <option value="-server"/> </jvm-options> </jvm> <jvm name="Test"> <heap size="164m" max-size="1256m"/> <permgen size="128m" max-size="128m"/> </jvm> </jvms> {code} Version-Release number of selected component (if applicable): How reproducible: ================= Steps to Reproduce: 1. See https://issues.jboss.org/browse/HAL-642
Here is a simple fix: PR (on maintenance branch): https://github.com/hal/core/pull/36 PR (on master): https://github.com/hal/core/pull/37
Heiko Braun <ike.braun> updated the status of jira HAL-642 to Resolved
I just verified it's already fixed in EAP 6.4.6.
Verified on EAP 6.4.7.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.