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

[Lyle Wang (JIRA)]

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

Lyle Wang commented on WFCORE-923:
----------------------------------

Hi, Alexey:

I think it would be great if it can cancel the current operation and return a error message telling which task it timed out. Is that possible ?

In some customer reported cases we see customer using a batch script file to execute  a set of commands in which, some time-consuming (e.g. upgrade database schema in a deployment) tasks are included. And sometime customer observe that the CLI gets hang up and will not return back.

What customer does now is, to write their own script and "spawn the CLI process in the background and watch the background PID for nnn seconds, and kill it myself if it doesn't complete."

Hope these explain. Thanks

Lyle.

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