Selenium Grid 2.49.0 throwing Timeout's (Session [d3e1b70c-4a81-4a1c-8916-b050106da3d9] was terminated due to TIMEOUT)

[smccarthy]

Windows 7 VM has the hub and the node.

Test :

import java.net.URL;
import java.util.concurrent.TimeUnit;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.testng.annotations.Test;

public class TestSeleniumGrid249 {
    @Test
    public void testSeleniumGrid249() throws Exception {
        DesiredCapabilities capabilities = DesiredCapabilities.chrome();
        WebDriver driver = new RemoteWebDriver(new URL("http://172.27.1.146:4444/wd/hub"), capabilities);
        Thread.sleep(5000);
        driver.manage().timeouts().setScriptTimeout(10, TimeUnit.SECONDS); // fails here
    }
}

Start Node: java -Dwebdriver.ie.driver=\tmp\webdriver\iedriver\iedriver_2.48.0_Win32bit.exe -Dwebdriver.chrome.driver=\tmp\webdriver\chromedriver\chromedriver_2.20_32bit.exe -jar C:\tmp\webdriver\2.49.0.jar -role wd -nodeConfig node_5555_1.json

Start Hub: java -jar C:\tmp\webdriver\2.49.0.jar -role hub -hubConfig hub_4444_1.json

Hub Json:

{
  "port": 4444,
  "newSessionWaitTimeout": 25000,
  "nodePolling": 5000,
  "cleanUpCycle": 5000,
  "browserTimeout": 120000,
  "timeout": 120000,
  "maxSession": 5
}

Node Json:

{
  "capabilities": [
    {
      "seleniumProtocol": "WebDriver",
      "browserName": "internet explorer",
      "maxInstances": 1,
      "version": "11"
    },
    {
      "seleniumProtocol": "WebDriver",
      "browserName": "chrome",
      "maxInstances": 3,
      "version": "47"
    },
    {
      "seleniumProtocol": "WebDriver",
      "browserName": "firefox",
      "maxInstances": 3
    }
  ],
  "configuration": {
    "maxSession": 3,
    "port": 5555,
    "hubPort": 4444,
    "hubHost": "127.0.0.1"
  }
}

[smccarthy]

Sorry I forgot to mention, it fails on Chrome, Firefox, and IE11 for me on Windows 7. It worked with the 2.48.2 jar file.

[smccarthy]

I also tried the exact same script on OSX (with Firefox) and it failed the same way.

Edit : I did notice increasing the cleanUpCycle in my hub config did make this specific test case pass.

[BenChand]

I had the same issue earlier with VMs on a selenium grid. Removing the Thread.Sleep from my test fixed it for me.

[smccarthy]

@BenChand I wanted my test to take longer than 5 seconds. That is why I used Thread.sleep(5000);

[BenChand]

@smccarthy Maybe try a driver wait with a timeout and catch the exception it will throw. At least the selenium session will know you are pausing it for a reason that way.

[hablijack]

Same problem here: I'm using https://github.com/codeborne/selenide and it waits for ajax requests ...
With 2.48.2. everything worked fine and with 2.49 i'm getting: "was terminated due to TIMEOUT".

[azohra]

We run into it in a test where we are waiting for an email to arrive and refresh the page every 5 seconds to check if it is there. We reduced the sleep but even at 3 seconds it happens on occasion. Seemingly, if the interval poller pings during a sleep/wait - it reports back that the browser session is dead and terminates the connection.

its not clear if this is a feature which was broken in previous releases, or a bug newly introduced in .49
The timeout logic itself makes sense, would be interesting to understand why the same failures do not occur in .48

[barancev]

Fixed by 545fba4

[azohra]

all hail @barancev !! cheers mate.

[barancev]

The fixed version 2.49.1 is available for download

[foxrafi]

cool, thanks for the fix