[
https://issues.jboss.org/browse/WFLY-10872?page=com.atlassian.jira.plugin...
]
Paul Ferraro commented on WFLY-10872:
-------------------------------------
The reason this fails is because there is only 1 load provider allowed at a given time,
and the current load provider is the dynamic one. Consequently, the existing load
provider needs to be removed first. The error message is admittedly confusing, since the
operation executed is not the same as the one entered, meaning:
/subsystem=mod_cluster/mod-cluster-config=configuration:write-attribute(name=simple-load-provider,
value=0)
will actually execute:
/subsystem=mod_cluster/mod-cluster-config=configuration/load-provider=simple:write-attribute(name=factor,
value=0)
What we should do is validate the existence of the load-provider=simple resource first and
use a more contextual message rather than the current one.
Missing translation for writing simple-load-provider attribute in
mod_cluster subsystem
---------------------------------------------------------------------------------------
Key: WFLY-10872
URL:
https://issues.jboss.org/browse/WFLY-10872
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 14.0.0.Beta2
Reporter: Jan Kašík
Assignee: Paul Ferraro
Priority: Blocker
Following should add simple load provider with factor=0:
{code}
/subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=simple-load-provider,
value=0)
{code}
Instead, this error shows up:
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"modcluster\"),
(\"proxy\" => \"default\"),
(\"load-provider\" => \"simple\")
]' not found",
"rolled-back" => true
}
{code}
There is missing translation to create the resource, same is the situation for undefine
operation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)