[
https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug...
]
Yeray Borges Santana commented on WFCORE-4970:
----------------------------------------------
Hello [~parsharma], in response to your question about this issue, at first glance, it
looks like the cause is all
the [JvmAttributes|https://github.com/wildfly/wildfly-core/blob/master/ho...
are not flagged as
[
RESTART_JVM|https://github.com/wildfly/wildfly-core/blob/master/controlle...].
It has to be verified where those attributes are being used and see if there is any CI
test failing, though, but it could be a possible fix.
It is suspicious that nobody has changed them before. [~jmesnil] / [~brian.stansberry] Do
you know beforehand if there is any reason why the JvmAttributes are not flagged as
Restart JVM?
Changing the JVM settings at host level does not put the servers in
restart-required
------------------------------------------------------------------------------------
Key: WFCORE-4970
URL:
https://issues.redhat.com/browse/WFCORE-4970
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 12.0.0.Beta2
Reporter: Yeray Borges Santana
Assignee: Parul Sharma
Priority: Major
Operations like the following one should put the servers in restart required to indicate
the user changes will be applied after restarting the servers:
{noformat}
[domain@localhost:9990 /] /host=master/jvm=default:write-attribute(name=heap-size,
value=256m)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)