James Perkins created WFCORE-788: ------------------------------------ Summary: Executing a composite operation allowing services to restart fails if the first operation relies on a capability of a remove operation Key: WFCORE-788 URL: https://issues.jboss.org/browse/WFCORE-788 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: Brian Stansberry 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)