[jboss-jira] [JBoss JIRA] (WFCORE-263) Cancelling management op on slave HC tree is broken

[James Livingston (JIRA)]

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

James Livingston commented on WFCORE-263:
-----------------------------------------

I've attached a simple reproducer with an @Startup @Singleton EJB that block forever in it's @PreDestroy. To use:
1) build with maven
2) start the host-master and host-slave configurations we ship
3) Deploy it and assign to the main group which runs on the slave HC
4) Attempt to remove the deployment
5) Poke around in the CLI

> Cancelling management op on slave HC tree is broken
> ---------------------------------------------------
>
>                 Key: WFCORE-263
>                 URL: https://issues.jboss.org/browse/WFCORE-263
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.0.Alpha9
>            Reporter: James Livingston
>            Assignee: Brian Stansberry
>         Attachments: unundeployable.zip
>
>
> If you have a DC with a slave HC, and perform a management operation which gets stuck, non-progressing operations will be reported for both the DC and the slave HC via:
> /host=master/core-service=management/service=management-operations:find-non-progressing-operation
> /host=slave/core-service=management/service=management-operations:find-non-progressing-operation
> Cancelling the operation under /host=master works as expected, pushing the cancellation down to the slave and the controllers become responsive again.
> If however you attempt to cancel the operation under /host=slave, it goes bad. { "outcome" => "success", "result" => undefined } is reported in the CLI, but the controllers are still unresponsive.
> Running :find-non-progressing-operation against the slave will report the {outcome=success,result=undefined} rather than that no non-progressing operations were found, and active-operation=*:read-resource() shows it as not cancelled.
> Once you attempt to cancel it on a slave, attempting to cancel it under /host=master will report success, but leave the slave op in a weird state, and things requiring the controller lock (such as the web UI) will still not respond.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)