Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
[domain@localhost:9990 /] undeploy 2e3b75f2-88ff-4eb9-a8b1-9107c452309e.ear --all-relevant-server-groups Undeploy failed: JBAS010839: Operation failed or was rolled back on all servers.
There are several issues at play here:
- Insufficient information is displayed along with JBAS010839
- No actual failure logged either in DC or in individual host's logs
- Failure to find a deployment unit on a particular host should not result in a failure of a domain-wide undeploy in DeploymentUndeployHandler
I'll start in a reverse order of causation:
In DeploymentUndeployHandler.execute
public void execute(OperationContext context, ModelNode operation) throws OperationFailedException { ModelNode model = context.readResourceForUpdate(PathAddress.EMPTY_ADDRESS).getModel(); ...
OperationContextImpl.readResourceForUpdate calls OperationContextImpl.requireChild:
private static Resource requireChild(final Resource resource, final PathElement childPath, final PathAddress fullAddress) { if (resource.hasChild(childPath)) { return resource.requireChild(childPath); } else { PathAddress missing = PathAddress.EMPTY_ADDRESS; for (PathElement search : fullAddress) { missing = missing.append(search); if (search.equals(childPath)) { break; } } throw ControllerMessages.MESSAGES.managementResourceNotFound(missing); } }
The exception generated by throw ControllerMessages.MESSAGES.managementResourceNotFound(missing);:
- does not propagate from the host to DC and to CLI
- is not logged with any level (not even TRACE) either on host or DC
- should be handled within DeploymentUndeployHandler not to fail the undeploy operation in case of a partially failed deployment (e.g. EAR with unsatisfied CDI dependencies).
Attachments
Issue Links
- relates to
-
JBEAP-7982 Improve CLI return messages in case of JBAS010839
- Closed
-
WFLY-4212 REGRESSION: CDI application fails to deploy in 8.2.0 vs 8.1.0
- Closed