[jboss-jira] [Red Hat JIRA] (WFCORE-4970) Changing the JVM settings at host level does not put the servers in restart-required
[
https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on WFCORE-4970:
------------------------------------------
I didn't find any cases where setRestartJvm was used on an attribute where the meaning
wasn't that the process that hosts the resource with that attribute needs to be
restarted. The JVM attributes are all in domain.xml or host.xml, so that means it is the
HC that hosts those resources. And we do not want the HC to get in restart-required.
So, -1 to setRestartJvm.
[~yersan] can explain what I mean about arbitrary descriptors, as I'll not be able to
focus on this issue.
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)