Thanks Ignasi, Andrew Sure i will check setting these properties and see if this issue is due to network fluctuations.
Thanks & regards, Poornima.BS On Fri, Dec 9, 2016 at 10:53 PM, Ignasi Barrera <n...@apache.org> wrote: > I don't really know why you are seeing this intermitent issue, but I > with Andrew in that it might be something related to the network. > > In any case, you can try to tweak your code by changing the value of > the following properties (all in ms): > > * jclouds.connection-timeout > * jclouds.ssh.max-retries > > HTH! > > I. > > On 9 December 2016 at 05:48, Poornima BS <poornimabs.g...@gmail.com> > wrote: > > Hi Andrew, > > > > Thanks for your reply. > > > > During launch of an instance itself i get this connect timeout issue > hence > > cannot test from command line. > > > > This issue does not pop up every time, only some times. I am not able to > > figure if i have to use set timeout property by overriding. > > > > Please find the below pastie link, > > > > http://pastie.org/private/ek9xmrtqjtml26n1eyky6a > > > > As u said it might be network issues but if thats the case how to handle > > such requests. > > > > Once i come across the connection timeout issue i wont get response back, > > since i have created launch an instance as a service in sping boot. > > > > Any suggestion would be appreciated. Please let me know if the > information > > is sufficient. > > > > Thanks & Regards, > > Poornima.BS > > > > > > On Thu, Dec 8, 2016 at 8:28 PM, Andrew Phillips <aphill...@qrmedia.com> > > wrote: > > > >> Hi Poornima > >> > >> (poornimabs:rsa[fingerprint(7a:58:70:0f:37:55:8b:17:62:33:72 > >>> :8d:7f:06:bc:b8),sha1(80:6e:02:0a:7d:bf:1d:6c:9c:35:04:63:39 > >>> :d6:d8:76:5c:68:45:e2)]@ > >>> 54.89.207.228:22) error acquiring {hostAndPort=54.89.207.228:22, > >>> loginUser=poornimabs, ssh=null, connectTimeout=60000, > >>> sessionTimeout=60000} > >>> (attempt 6 of 7): connect timed out > >>> > >> > >> Could you put an example of the code you are trying to run into a Gist > or > >> Pastie? I suspect that it may be worth trying a larger connection > timeout > >> setting (from the output above, it's currently set to 60s), but we would > >> need to see the code to be able to advise on how best to do that. > >> > >> However: if it takes longer than a minute to connect to some of your > >> target systems, I suspect you may have some network/infrastructure issue > >> going on that will continue to be a problem even if we configure a > longer > >> timeout. > >> > >> Do you get similar timeouts if you try to connect to that instance > without > >> using jclouds, e.g. from the command line? > >> > >> Regards > >> > >> ap > >> >
