[
https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug...
]
Parul Sharma edited comment on WFCORE-4970 at 2/11/21 10:16 AM:
----------------------------------------------------------------
I have flagged jvmAttributes as setRestartJvm() and run the customs CI job for
WFCORE-Master_linux_JDK 8 neither one is failing. Link of CI
job:https://ci.wildfly.org/viewLog.html?buildId=242451&buildTypeId=Wi...
was (Author: parsharma):
I have flagged jvmAttributes as setRestartJvm() and run the customs CI job for
WFCORE-Master_linux_JDK 8 neither one is failing. Link of CI
job: [https://ci.wildfly.org/viewLog.html?buildId=242451&buildTypeId=....
|https://ci.wildfly.org/viewLog.html?buildId=242451&buildTypeId=WildFlyCore_MasterLinux]
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)