[jboss-jira] [JBoss JIRA] (WFCORE-488) Failures of undeploy of a partially failed deployment
[
https://issues.jboss.org/browse/WFCORE-488?page=com.atlassian.jira.plugin...
]
Arcadiy Ivanov commented on WFCORE-488:
---------------------------------------
Firstly, while I appreciate moving this to WFCORE, this affects 8.2.0.Final first and
foremost and that's what should be targeted for a fix primarily as far as I'm
concerned, since I'm trying to move to WFLY 8.2.0.Final.
The process where exception is generated is a domain-controlled server on one of the
domain hosts, the exception is "org.jboss.as.controller.NoSuchResourceException:
JBAS014807: Management resource '[("deployment" =>
"7d829f16-ebd3-4c57-a14f-55e732e2e975.ear")]' not found"
It definitely doesn't propagate to CLI. I'll get back to you on whether it gets to
DC as an exception, in a form of {{step.response.get(FAILURE_DESCRIPTION).set(failDesc)}}
or not at all.
The reason the deployment resource was not present is a subject of a different regression
bug I'm going to be filing. An Arquillian EAR containing a WAR, an EJB jar and a
utility jar in the EAR/lib containing CDI beans injected by EJB jar fails to deploy due to
8.2.0.Final WELD not recognizing any of the synthetic beans in the utility jar as such and
failing to inject them into the EJB. This is a regression from 8.1.0.Final since the same
test has no issues deploying there.
Why this partial deployment state is inconsistent between the DC and domain-controlled
servers is a mystery and may be a result of some other domain-management bug.
My next step will be to come up with an isolated reproducible test and filing CDI
regression bug.
Failures of undeploy of a partially failed deployment
-----------------------------------------------------
Key: WFCORE-488
URL: https://issues.jboss.org/browse/WFCORE-488
Project: WildFly Core
Issue Type: Bug
Components: CLI, Domain Management
Reporter: Arcadiy Ivanov
Assignee: Alexey Loubyansky
{noformat}
[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.
{noformat}
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
{noformat}
public void execute(OperationContext context, ModelNode operation) throws
OperationFailedException {
ModelNode model =
context.readResourceForUpdate(PathAddress.EMPTY_ADDRESS).getModel();
...
{noformat}
OperationContextImpl.readResourceForUpdate calls OperationContextImpl.requireChild:
{noformat}
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);
}
}
{noformat}
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).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)