[ https://issues.jboss.org/browse/WFLY-5530?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5530: ---------------------------------------- There's a problem with how the deprecation of 'enable' / 'disable' works in a managed domain. The WFLYJCA0093 failure message reported here is reported if the op is sent to a server, but on the domain controller the op is handled as a no-op locally, and then propagated on to the servers affected by the relevant profile. This has some incorrect effects. Let's assume for the sake of illustration that the datasource is currently configured as enabled in the domain wide config, and then the 'disable' op is sent. The effect of this is: 1) If the profile is used by a current version server, the op will fail on that server, with the same WFLYJCA0093 failure message. Whether that results in a rollback of the op on the domain controller and across the domain depends on the rollout plan in use. A rollout plan could be specified that allows the failures on the servers. If this is the case, the operation outcome will be reported as 'success' but no change will have been made to the domain wide configuration (since the DC handles this op locally as a no-op.) This is an unintuitive result, since the user will reasonably expect that a 'success' will mean a change to the domain wide configuration has occurred. In all other cases involving ops that change configuration, 'success' means this. 2) If the profile is only used by legacy servers, then those servers will update their running configuration to disable the datasource, but configuration on the DC will not reflect this change, again because on the DC the op is handled locally as a no-op. Again, the operation outcome will be reported as 'success' but no change will have been made to the domain wide configuration. Basically, allowing an op that has historically resulted in a config change to execute on the DC without actually changing the domain wide config is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)