[
https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug...
]
Yeray Borges Santana commented on WFCORE-4970:
----------------------------------------------
Hello [~parsharma], thanks for looking at this.
{quote}RESTART_JVM neither the CI test is failing.
{quote}
I understand you have changed all the JvmAttributes and verified that there are no CI
errors, can you confirm whether I am understanding it correctly? If so, it would be great
to have a CI job link.
In general, yes the fix should be that one, adding that flag to those attributes. However,
as Brian pointed out before, it is very important to have pretty clear where those
attributes are being used because they could be used by different management operations on
different resources. Before proceeding with these changes we need to have pretty clear
which operations are using these attributes, and then we need to verify that the execution
of those operations requires a restart of the JVM that is being administered.
To continue progressing on this, we could have here, in this Jira as a commentary, a list
of all the resources where we can be using these JvmAttributes in management operations.
Sadly, I thought this issue was easier, but as we have discovered, it will require an
amount of concise work analyzing the code and documenting its uses first.
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)