[
https://issues.apache.org/jira/browse/JCLOUDS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615460#comment-15615460
]
Ignasi Barrera commented on JCLOUDS-1192:
-----------------------------------------
The script timeout is not a "connection" timeout. That timeout is used to wait
until the script execution completes, but in this case I think it won't help
you, since jclouds wouldn't be able to connect to the node to determine the
exit status of the script.
You could try running the script asynchronously by calling the
[submitScriptOnNode|http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/compute/ComputeService.html#submitScriptOnNode(java.lang.String,%20java.lang.String,%20org.jclouds.compute.options.RunScriptOptions)]
method. This method returns a future that behaves exactly as the
{{runScriptOnNode}} method when you call its {{get()}} method, but you should
be able to just let it run in background and forget about it, or cancel it at a
given point in time.
Could you try this?
> TIMEOUT_SCRIPT_COMPLETE doesn't work.
> -------------------------------------
>
> Key: JCLOUDS-1192
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1192
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-scriptbuilder
> Affects Versions: 1.9.2
> Reporter: Andrei
>
> Provided part of source code performs running _host_update.sh_ scripts via
> *runScriptOnNode* method. Mentioned script contains at the end command that
> performs new release in DHCP, and as result *ComputeService* lost connection
> and cannot return the *ExecResponse*. It leads to hung execution app. It has
> been tried to configure any timeouts, but it doesn't interrupt
> *runScriptOnNode* method in configured time.
> Operating System Version - Windows 10
> Java version - 1.8.0_102
> Part of source code could be found
> [here|https://gist.github.com/borodatu/dcf9248786b16a509fbea476f7f01e82]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
