[jboss-jira] [JBoss JIRA] (WFCORE-923) Execution timeout for CLI operations

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-923:
-----------------------------------------

This will try and cancel that op:

{code}
/core-service=management/service=management-operations/active-operation=-340841891:cancel
{code}

If you can attach a server-side thread dump it may shed some light on why it's not completing. The "execution-status" => "executing" shows it's not in the "blocking" points where on a standalone server the "blocking-timeout" value I mentioned above is used.

> Execution timeout for CLI operations
> ------------------------------------
>
>                 Key: WFCORE-923
>                 URL: https://issues.jboss.org/browse/WFCORE-923
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: CLI
>    Affects Versions: 2.0.0.Beta4
>            Reporter: Lyle Wang
>            Assignee: Alexey Loubyansky
>              Labels: cli, timeout
>
> It will be great if we could have a timeout setting to "stop-the-CLI-execution-after-nnn-seconds" , for all general CLI operations.
> Specifically, during some CLI operations, for example "deploy" or "reload", it is possible that things get stuck and hang-up, CLI cannot get back / return to the user after a long waiting. In this case, if we're able to setup an "execution timeout" and let CLI return with an error message, that would be much better. User should be able to know command execution results by viewing the related logs or checking the status.
> Currently there is "--timeout" setting when running "jboss-cli.sh", but that seems only effective on "connect" operation, tried to use this timeout with a CLI script file, which has "deploy"  inside (./jboss-cli.sh --file=test.cli --timeout=xxx), it doesn't work when the deployment takes a long time.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)