[jboss-jira] [JBoss JIRA] (WFCORE-488) Failures of undeploy of a partially failed deployment

[Arcadiy Ivanov (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029509#comment-13029509 ] 

Arcadiy Ivanov commented on WFCORE-488:
---------------------------------------

>> we are not actively working on further 8.x releases
If need be I'll backport and create a patch myself, not a problem. 

That said, I find it peculiar that the latest stable release of the container is abandoned as soon as it is released. I understand this is a community product and RH officially provides no support but it still is targeted at the enterprise audience so even though 9.0 will be the next latest and greatest, until it is so we still need to use 8.x versions as a current platform and bugs like this have to be fixed somehow. 

Maybe community patching/Service Pack effort should be initiated? I have no problem assembling my own WLFY with controlled patches applied, but it may be too cumbersome/advanced for some users.

>> I expect BlockingQueueOperationListener.operationFailed to be invoked on the DC.
{{ServerUpdatePolicy.recordServerResult(ServerIdentity, ModelNode) line: 140}} receives the failure information, but the failure information doesn't seem propagate/attach to the originating operation/step.


> 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 at 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)