[ https://issues.jboss.org/browse/WFCORE-788?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-788: --------------------------------- Description: This does seem to be somewhat of an edge case as the only way to reproduce it is to add the {{allow-resource-service-restart=true}} header to a composite operation. The first operation must also need access to a capability provided by a resource being removed. It's likely an acceptable failure, but the failure isn't seen when executing the same composite operation again. The issue seems to be that the [capability is removed|https://github.com/bstansberry/wildfly-core/blob/discard-model/co...] on the first execution that fails and is rolled back. On the second execution of the composite operation there is no [capability registered|https://github.com/bstansberry/wildfly-core/blob/discard-model...] registered in the {{RuntimeCapabilityRegistration}} so the [remove|https://github.com/bstansberry/wildfly-core/blob/discard-model/con...] of the capability doesn't happen. This allows the first operation to pass. was: This seems to be somewhat of an edge case, but it does exist. In the reproduce instructions you'll see a {{disable}} followed by a {{remove}} composite operation fails if the {{allow-resource-service-restart=true}} is set. It's likely an acceptable failure, but the failure isn't seen when executing the same composite operation again. The issue seems to be that the [capability is removed|https://github.com/bstansberry/wildfly-core/blob/discard-model/co...] on the first execution that fails and is not added back. On the second execution of the composite operation there is no [capability registered|https://github.com/bstansberry/wildfly-core/blob/discard-model...] so the [remove|https://github.com/bstansberry/wildfly-core/blob/discard-model/con...] of the capability doesn't happen which makes the first step of the operation happy as the capability still exists. -- This message was sent by Atlassian JIRA (v6.3.15#6346)