[jboss-jira] [JBoss JIRA] (WFCORE-923) Execution timeout for CLI operations
Alexey Loubyansky (JIRA)
issues at jboss.org
Fri Sep 18 09:16:02 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13110427#comment-13110427 ]
Alexey Loubyansky commented on WFCORE-923:
------------------------------------------
What would you like the CLI to do in the case when deploy takes longer than expected? E.g.
Log a warning that it's taking too long.
Log an error and try to somehow undo the command.
Does the deploy actually succeed in your case even if it takes too long?
Thanks,
Alexey
> 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)
More information about the jboss-jira
mailing list