[jboss-jira] [JBoss JIRA] (WFCORE-4035) operation-requires-reload message is missing

金沢 栄治 (JIRA) issues at jboss.org
Tue Aug 14 20:10:00 EDT 2018


金沢 栄治 created WFCORE-4035:
-----------------------------

             Summary: operation-requires-reload message is missing
                 Key: WFCORE-4035
                 URL: https://issues.jboss.org/browse/WFCORE-4035
             Project: WildFly Core
          Issue Type: Bug
          Components: IO
            Reporter: 金沢 栄治
            Priority: Minor


when modify values of task-max-threads and task-keepalive,
operation-requires-reload message is not outputed.
these two attributes is processed in XnioWorker#setOption, and have values return,
so it should always return true.

---
[standalone at localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-keepalive, value=10000)
{"outcome" => "success"}
[standalone at localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-max-threads, value=10000)
{"outcome" => "success"}
[standalone at localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=io-threads, value=10000)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone at localhost:9990 /] /subsystem=io/worker=default:write-attribute(name=task-core-threads, value=10000)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
---



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)



More information about the jboss-jira mailing list