Bart1909
commented
5 years ago Try to set the connectionTimeoutMillis options-parameter to a higher value. This worked for me
Open ehankamo opened 7 years ago
Bart1909
commented
5 years ago Try to set the connectionTimeoutMillis options-parameter to a higher value. This worked for me
I am running into this exception when attempting to call an IO that takes more than 150 seconds to return. Now, when I run this against a Windows 2008 target, it runs fine and respects the 1800 operationtimeout limit that is set. In Windows 2012, it always times out after about 150 seconds. I looked at the target server's WinRM settings and they match the 2008 server. It is throwing the exception well under the MaxTimeoutMs setting on the 2012 WinRM client. Any idea what could be causing this mysterious exception?
To verify this was a timeout exception, i wrote a sleep script and it's consistently timing out after 150 seconds.
I found a potential and crude workaround where if I spawn off a "ping" command that runs in the background every second while the IO is running at the same time, it will keep the session alive and allow the IO to complete after some time.... but I really do not want to go there yet because I am having trouble killing the ping (runs forever or I have to set some finite number of times for it to ping).
Below is the output in the XLD log. When deploying to the Win 2012 server
` **"start sleep" Step failed com.xebialabs.overthere.cifs.winrm.WinRmRuntimeIOException: Error when sending request to https://w438717.internal.foo.com:5986/wsman Request:
<?xml version="1.0" encoding="UTF-8"?>