[jboss-jira] [JBoss JIRA] (WFLY-3090) Administrative cancellation of management ops results in closed connections

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-3090:
----------------------------------------

That can be done within the operation execution code with appropriate interruption handling. Agreed it would be nicer to have been control over whether interruption happens vs some other mechanism though.

I think the "too late" state would really just be on the return path after the op commits, and perhaps not in the rollback case though. (It's possible for a hang to occur during rollback waiting for MSC stability; that should be interruptible with the process ending up in a restart-required state.) But before the op gets to that state it writes; e.g. the "prepared" message in a transactional op.
                
> Administrative cancellation of management ops results in closed connections
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-3090
>                 URL: https://issues.jboss.org/browse/WFLY-3090
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.0.0.Final
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 9.0.0.CR1
>
>
> Administrative cancellation of management ops is implemented by the thread that is handling the cancellation interrupting the thread that is executing the op. This works, but the thread executing the op can't readily distinguish between interruption do to admin action and cancellation for other reasons such as server shutdown. The OperationContext code detects interruption but restores the interrupted state to the thread, which is valid for the shutdown case. For the administrative cancellation case, it has the negative side effect of producing InterruptedExceptions later on; e.g. when the thread attempts to send data to the remote caller.
> This is particularly an issue in domain mode where the "caller" is a controlling process (HC). The InterruptedException has the effect of terminating the connection from the callee to the controlling process.
> The operation execution code needs to be able to distinguish between administrative cancellation and other causes of interruption.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira