[
https://issues.jboss.org/browse/AS7-3169?page=com.atlassian.jira.plugin.s...
]
Pavel Slegr commented on AS7-3169:
----------------------------------
What are actually the allowed values ?
Are there any restrictions for name ?
For heap sizes we could have some like...[\\d]{2,4}[mM] Depends if we want to allow m/M
after at least 2 and at most 4 digits...
Admin console: missing validation on JVM arguments
--------------------------------------------------
Key: AS7-3169
URL:
https://issues.jboss.org/browse/AS7-3169
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Pavel Slegr
Priority: Critical
Attachments: jvmargs.png
It is currently possible to set invalid JVM arguments for a server instance or group, as
seen in the attached screenshot. The input field designating heap size and maximum heap
size should be somehow reworked, made more intuitive, at least the help should show more
information on what you can put in. If you enter an invalid value, the operation will
succeed, the invalid value will be used after the domain is restarted, and causing related
servers to NOT BOOT UP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira