[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=13169104#comment-13169104 ] 

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

Just an FYI:  there is a blocking-timeout header that can be applied to all management operations. It's really not the same thing as an execution timeout though. Value is in seconds.

1) It's a server side timeout, not client side, so if for some reason execution doesn't complete due to some issue between the client and server, it has no impact.

2) It's not an overall limit on execution time. Rather, it controls how long blocking is allowed to continue in various points in the operation execution where the execution thread blocks waiting for some condition to be met (e.g. MSC service container stability, or responses from other processes in a managed domain.) The overall execution time can be longer than the blocking timeout though. For example with a domain-wide operation that is configured to roll out to each server in series, the blocking time per server could be fairly small, but with a lot of servers the overall time would be large.

The default value is 300s. It's basically meant to act as a failsafe to prevent blocking forever, with the header allowing users to set a lower or higher limit for unusual cases where they either know things will take a long time, or they know 300s is way too much and they want more rapid failure.

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