[
https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on WFCORE-4970:
------------------------------------------
[~yersan] The only thing I can think of is that they don't require restart of the JVM
that is being administered, which is the HC. It's important to be careful about the
meaning of that piece of metadata. If we're already messy about that distinction in
other similar cases, please note that here. If we're not we should be very careful
about not introducing new meanings into the read-resource-description output.
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)