[ https://issues.jboss.org/browse/WFLY-10872?page=com.atlassian.jira.plugin... ] Paul Ferraro edited comment on WFLY-10872 at 8/20/18 10:13 AM: --------------------------------------------------------------- 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 (adding the load-provider=simple will also do this). 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. was (Author: pferraro): 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. -- This message was sent by Atlassian JIRA (v7.5.0#75005)