search

SeleniumHQ / selenium-google-code-issue-archive

Archive, please see main selenium repo
https://github.com/seleniumhq/selenium
346 stars 194 forks source link

[Firefox 19]After servel hours' long run, org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.... Caused by: java.net.SocketTimeoutException: Read timed out #5414

Open lukeis opened 8 years ago

lukeis commented 8 years ago

Originally reported on Google Code with ID 5414

I'm trying to run a 24 hours' long run using WebDriver with firefox 19, and I can ALWAYS
meet this issue.

I'm using Java, Eclpise, Firefox 19 and Selenium 2.3.0 Webdriver, not using webserver.
My test browser and eclipse are installed on the same PC(window XP), selenium-java-2.30.0.jar
&  selenium-server-standalone-2.30.0.jar are imported to my automation test project.

How long after long run to reproduce this issue is uncertain. The short one took round
1 hour and longest once took 20 hours.

My test scenario is calling sendKeys iteratively to keep entering text into a rich
text editor, about 3-4 character per second. Judged by selenium log, the last sendKeys
action took place at 6:51:43, then selenium seems lost contact with browser, no more
log generated. Firefox is still there and the automation program is still runing, but
no more log and selenium do not interact with firefox anymore. And exactly 3 hours
later at 9:51:44, the UnreachableBrowserException exception was caught, the automation
programe was termintaed then.
--------------Below is the Exception-----------------------
Time:2013-03-27:215144
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.30.0', revision: 'dc1ef9c', time: '2013-02-19 00:15:57'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1 build 2600 Service
Pack 3', java.version: '1.6.0'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
    at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:89)
    at com.ibm.concord.automation.appobjects.upper.ConcordWebElement.sendKeys(ConcordWebElement.java:215)
    at com.ibm.concord.automation.appobjects.upper.RootDocument.sendKeysWithInterval(RootDocument.java:248)
    at com.ibm.concord.automation.tasks.LotusLiveDocument.inputText(LotusLiveDocument.java:459)
    at com.ibm.concord.automation.testcases.document.DocumentCoEditTestCase_Sharer.runTest(DocumentCoEditTestCase_Sharer.java:57)
    at com.ibm.concord.automation.testcases.BaseTestCase.runTestCase(BaseTestCase.java:64)
    at com.ibm.concord.automation.testcases.BaseTestCase.main(BaseTestCase.java:115)
Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:141)
    at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:166)
    at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:90)
    at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:281)
    at org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:92)
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:62)
    at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)
    at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)
    at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)
    at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
    at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:712)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:517)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
    at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:332)
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:311)
    at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:133)
    at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:355)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:527)
    ... 8 more

----------------------Below are selenium logs------------------------
Mar 27, 2013 6:51:42 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executing: sendKeysToElement [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["n"]}]
Mar 27, 2013 6:51:43 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executed: [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement {"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["n"]}]
Mar 27, 2013 6:51:43 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executing: sendKeysToElement [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["a"]}]
Mar 27, 2013 9:51:44 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Exception: [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement {"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["a"]}]
Abalo_000_001_Bank0 # END OF TESTCASE: com.ibm.concord.automation.testcases.LLiNotesBase

From the log,you can see the last sendKeys action took place at 6:51:43, and the exception
was thrown at 9:51:44, which took exactly 3 hours after webdriver lost contact with
firefox. 

-----------------below is my Java code snippet----------------
//The method to keep sendKeys iteratively
public int sendKeysWithInterval(WebElement element, String keys, double interval, int
start) {
    for (int i = start; i < keys.length(); i++) {
        try {
            if ("\n".equals(keys.charAt(i) + ""))
                element.sendKeys(Keys.ENTER);
            else
                element.sendKeys(keys.charAt(i) + "");  //Exception source is here
            Thread.sleep(100);
        } catch (StaleElementReferenceException e) {
            rootdriver
                    .logWarning("StaleElementReferenceException occured while sendKyes:"
                            + keys.charAt(i) + ":" + e.getMessage());
            return i;
        }
    }
    return keys.length();
}
....

//The way I start my FirefoxWebDriver
FirefoxProfile profile = new FirefoxProfile();
profile.setEnableNativeEvents(true);
RemoteWebDriver driver = new FirefoxDriver(profile);
concorddriver = new ConcordWebDriver(driver);

Reported by eminemheaton on 2013-03-28 03:25:36

lukeis commented 8 years ago 
I'm sure this is not relative with reach TCP port limit. I've set the max limit count
to 65534, and the TCP/UDP link on my PC is around 300, far from the max limit.

Reported by eminemheaton on 2013-03-28 03:34:02

lukeis commented 8 years ago 
I know we have a similiar issue 3000, but mine is Firefox only, and the exception is
caused by "java.net.SocketTimeoutException: Read timed out"
I commented in 3000 and opened this new one. 

This is urgent for me, thanks for understanding!

Reported by eminemheaton on 2013-03-28 03:45:34

lukeis commented 8 years ago 
I'm start to thinking this might becasue I called the element.sendKeys fucntion too
often.
I slowdown the speed and re-run the test again, any finding will be posted here.

Reported by eminemheaton on 2013-03-28 10:40:56

lukeis commented 8 years ago 
I slowed down the sendKeys speed from 136 characters per second to 60 characters per
second, unfortunately around 9 hours after the test was kicked off I still meet the
same issue again.

Reported by eminemheaton on 2013-03-29 01:14:43

lukeis commented 8 years ago

Reported by barancev on 2013-03-29 19:31:24

lukeis commented 8 years ago 
Hi,

I am getting the same issue. When trying to run more than 200 Testcases, 2 of these
executed testcases threw Exception after 3 Hours.

Browser: Firefox v20.0
Selenium Server Version: 2.32
Platform: Windows 7 64-bit & Windows XP 32-bit
Start time: 01:04:42 PM
End (Exception occurred) time: 04:05:06 PM

Error Details: 
Error communicating with the remote browser. It may have died. Build info: version:
'2.32.0', revision: '6c40c18', time: '2013-04-09 17:22:56' System info: os.name: 'Windows
7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_10' Driver info: driver.version:
RemoteWebDriver Caused by: java.net.SocketTimeoutException: Read timed out

Error communicating with the remote browser. It may have died. Build info: version:
'2.32.0', revision: '6c40c18', time: '2013-04-09 17:22:56' System info: os.name: 'Windows
XP', os.arch: 'x86', os.version: '5.1', java.version: '1.7.0' Driver info: driver.version:
RemoteWebDriver Caused by: java.net.SocketTimeoutException: Read timed out

Reported by santhosh.vsk on 2013-05-30 06:00:54

lukeis commented 8 years ago 
Hello,

Please provide some feedback. When is it going to be fixed? Which previous version
doesn't have this bug?

I've faced it on following test environments:

Browsers: Google Chrome v26.0 and v27.0, IE9
Platform: Windows 7, Windows XP

Error Details Sample:
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.31.0', revision: '1bd294d185a80fa4206dfeab80ba773c04ac33c0',
time: '2013-02-27 13:51:26'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_35'
Driver info: driver.version: RemoteWebDriver

Caused by: org.openqa.selenium.WebDriverException: java.net.SocketTimeoutException:
Read timed out
Build info: version: '2.31.0', revision: '1bd294d185a80fa4206dfeab80ba773c04ac33c0',
time: '2013-02-27 13:51:26'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_35'
Driver info: driver.version: RemoteWebDriver

Reported by tonya.paslavska on 2013-06-05 09:00:15

lukeis commented 8 years ago 
Hello, 

I am also facing the same issue. I am facing the issue on firefox21, chrome27.

Reported by mannchoyal on 2013-06-25 11:50:28

lukeis commented 8 years ago 
Hi All,

Any updates on this issue.
This issue is seen in chrome driver as well.
A workaround will be appreciated here.

Thanks
Jaffer

Reported by jaffer@owler.com on 2013-07-23 13:52:44

lukeis commented 8 years ago 
meet the same issue, seems when the webdriver cannot find some element exactly for 3
hoours , it will throw this exception. 
here  is my logs:
Jul 31, 2013 9:02:38 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executing: sendKeysToElement [d05f77e1-ee34-4668-a695-19abbab2659e, sendKeysToElement
{"id":"{f4db0abf-b4cb-4e24-a8d0-4b49cc2df145}","value":["p"]}]
Aug 1, 2013 12:02:38 AM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Exception: [d05f77e1-ee34-4668-a695-19abbab2659e, sendKeysToElement {"id":"{f4db0abf-b4cb-4e24-a8d0-4b49cc2df145}","value":["p"]}]
Time:2013-08-01:000238
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.30.0', revision: 'dc1ef9c', time: '2013-02-19 00:15:57'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_17'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:89)
at com.ibm.concord.automation.appobjects.upper.ConcordWebElement.sendKeys(ConcordWebElement.java:215)
at com.ibm.concord.automation.appobjects.upper.RootDocument.sendKeysWithInterval(RootDocument.java:248)
at com.ibm.concord.automation.tasks.LotusLiveDocument.inputText(LotusLiveDocument.java:293)
at com.ibm.concord.automation.testcases.document.DocumentCoEditTestCase_Owner.runTest(DocumentCoEditTestCase_Owner.java:52)
at com.ibm.concord.automation.testcases.BaseTestCase.runTestCase(BaseTestCase.java:61)
at com.ibm.concord.automation.testcases.BaseTestCase.main(BaseTestCase.java:109)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:166)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:90)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:281)
at org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:92)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:62)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:712)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:517)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:332)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:311)
at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:133)
at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:355)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:527)
... 8 more

Reported by EvanHon1987 on 2013-08-01 06:54:38

lukeis commented 8 years ago 
Hi All,

Facing the same issue. We are working with Selenium 2.25, ie 8, Windows 7. Below is
my error log.

org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session.
Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 22:18:01'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_17'
Driver info: driver.version: InternetExplorerDriver
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
    at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
    at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
    at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
    at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
    at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
    at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
    at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
    at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
    at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:66)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:182)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:167)
    at org.openqa.selenium.ie.InternetExplorerDriver.startSession(InternetExplorerDriver.java:133)
    at org.openqa.selenium.ie.InternetExplorerDriver.setup(InternetExplorerDriver.java:106)
    at org.openqa.selenium.ie.InternetExplorerDriver.<init>(InternetExplorerDriver.java:52)
    at com.tcs.bancs.testframework.api.DefaultTestContextConfigurer.getDrivers(DefaultTestContextConfigurer.java:99)
    at com.tcs.bancs.testframework.impl.GuiModTestRunner.runChild(GuiModTestRunner.java:68)
    at com.tcs.bancs.testframework.impl.GuiModTestRunner.runChild(GuiModTestRunner.java:28)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
    at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
    at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159)
    at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)

Reported by deepa.deepanair on 2013-08-29 11:23:03

lukeis commented 8 years ago 
This seems like a much higher priority to me than a "Medium" priority bug.  I have an
immediate project requirement for long-running Selenium tests and can't deliver a product
broken in this way. 

Also seeing this under Windows 7 in VMWare against IE 11:

  org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with
the remote browser. It may have died.
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'Andy-PC', ip: '192.168.1.2', os.name: 'Windows 7', os.arch: 'amd64',
os.version: '6.1', java.version: '1.7.0_45'
Driver info: driver.version: RemoteWebDriver
  at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
  at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:268)
  at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:79)
  at com.sdlgov.mflts.selenium.specs.JobElement$$anonfun$toggleSelected$1.apply$mcV$sp(JobElement.scala:43)
  at com.sdlgov.mflts.selenium.specs.JobElement$$anonfun$toggleSelected$1.apply(JobElement.scala:41)
  at com.sdlgov.mflts.selenium.specs.JobElement$$anonfun$toggleSelected$1.apply(JobElement.scala:41)
  at com.sdlgov.mflts.selenium.utils.DriverHelpers$class.safeDriverAction(DriverHelpers.scala:47)
  at com.sdlgov.mflts.selenium.specs.JobElement.safeDriverAction(JobElement.scala:12)
  at com.sdlgov.mflts.selenium.specs.JobElement.toggleSelected(JobElement.scala:41)
  at com.sdlgov.mflts.selenium.pages.T2TWidgetPage$$anonfun$deleteAllJobs$1$$anonfun$apply$mcV$sp$2.apply(T2TWidgetPage.scala:84)

Reported by apolack@sdlgov.com on 2014-01-23 20:55:53

lukeis commented 8 years ago 
We have the same problem with Selenium 2.41 and Firefox 28.0 running on Debian Linux
2.6.32. It happens regularly (every day) on different methods.

Our different tests also run for hours and the hang happens regularly (every day) for
instance like this (but it sometimes happens also on other methods):

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died. Build info: version: '2.41.0', revision: '3192d8a6c4449dc285928ba024779344f5423c58',
time: '2014-03-27 11:29:39' System info: host: 'replaced', ip: '127.0.0.1', os.name:
'Linux', os.arch: 'amd64', os.version: '2.6.32-5-amd64', java.version: '1.7.0_10' Driver
info: driver.version: RemoteWebDriver at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:589)
at org.openqa.selenium.remote.RemoteWebDriver.findElements(RemoteWebDriver.java:373)
at org.openqa.selenium.remote.RemoteWebDriver.findElementsByXPath(RemoteWebDriver.java:449)
at org.openqa.selenium.By$ByXPath.findElements(By.java:352) at org.openqa.selenium.remote.RemoteWebDriver.findElements(RemoteWebDriver.java:336)
at org.jahia.selenium.functions.BasicSeleniumFunctions.isElementDisplayed(BasicSeleniumFunctions.java:599)
at org.jahia.selenium.functions.LoginFunctions.fillLoginForm(LoginFunctions.java:137)
at org.jahia.selenium.functions.LoginFunctions.loginToPath(LoginFunctions.java:124)
at org.jahia.selenium.scripts.editPanel.LeftPanelSearchTest.leftPanelSearchTest(LeftPanelSearchTest.java:63)
Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native
Method) at java.net.SocketInputStream.read(SocketInputStream.java:150) at java.net.SocketInputStream.read(SocketInputStream.java:121)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:160)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:84)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:273)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:223)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:322)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:301)
at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:165)
at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:362)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:568) ...
35 more ... Removed 27 stack frames 

Now we would also be interested to have a lower timeout than 3 hours like mentioned
in issue 3951, but I would like to find the error, which is causing this hang.

Actually when this happens Firefox has not crashed and is totally responsive. I do
thread dumps and see that on the selenium side we already hang in the socket read.
 I open the Error console on Firefox and every time when this 3 hours hanging starts
to happen I see the line: "Lost DOM in window undefined". 

What is also interesting is that manually clicking F5 to refresh the Firefox page suddenly
awakens the driver and the test continues without the read timeout and the following
UnreachableBrowserException.

Perhaps I should also mention that our web application uses an iframe, but don't know
if that could cause the issue. I assume the cause of the hang bug to be on the Firefox
side in the webdriver plugin, but there I don't know yet how to dig deeper and get
more info and would appreciate any help to find the cause of the hangs.

Reported by bpapez@jahia.com on 2014-06-04 07:54:35

lukeis commented 8 years ago 
If hitting 'F5' seems to refresh the page, can you just manually send 'F5' when an UnreachableBrowserException
occurs as a work-around?

I ultimately wound up just killing and restarting IE (and assorted test cases) when
I encountered this issue.  I believe the root causes are many and varied... my suspicion
is that this is due to Selenium not really being designed to run over long periods
of time - my understanding is that it was meant to automate functional tests, not longevity
tests. :-(

Perhaps I'm wrong, but in the 2-ish years I've been using Selenium intermittently,
support for browsers, especially in these long-running cases, does not seem to me to
have improved much.

Reported by apolack@sdlgov.com on 2014-06-04 09:31:00

lukeis commented 8 years ago 
We actually don't do yet intentional longevity tests, but running through our functional
test suites takes about 5 hours if everything is smooth. But because of these UnreachableBrowserException
it takes n x 3 hours longer, which makes it difficult to keep a schedule on our continuous
integration server.

So for one it would help if the timeout would be settable so we could set it to much
less than 3 hours and then react on that exception faster. On the other side I would
be very interested to find the bug, which is causing the hang, if there is a way to
get more information or debug logging.

Reported by bpapez@jahia.com on 2014-06-04 11:20:32

lukeis commented 8 years ago 
any idea if this bug is worked on? thanks

Reported by flavius.nopcea@ubirimi.com on 2014-09-08 12:48:49

lukeis commented 8 years ago 
This same problem is happening for me on Chrome. Is it possible to remove the Firefox
tag from this issue and title to potentially get it more visibility? It's definitely
exclusive to Firefox 19 as the title implies.

Reported by tbliss11 on 2014-09-24 03:50:21

lukeis commented 8 years ago 
I wrote a blog how to fix this issue (as there are more ways how you can get UnreachableBrowserException):
http://matejtymes.blogspot.co.uk/2014/10/webdriver-fix-for-unreachablebrowserexc.html

Reported by MatejTymes on 2014-10-29 01:04:26

lukeis commented 8 years ago 
I'm having the same problem. 3 hours of server being stucked. That sux!

>> #19 MatejTy...@gmail.com
I don't see, how your third solution should fix our problem using FirefoxDriver (extends
RemoteWebDriver). What is this PhantomJSDriver anyway?

Reported by flesnablizna on 2015-01-19 17:15:26

lukeis commented 8 years ago 
Go to this page: http://assertselenium.com/selenium-tips-tricks/
I just added: 
FirefoxBinary fb = new FirefoxBinary();
fb.setTimeout(java.util.concurrent.TimeUnit.SECONDS.toMillis(90));

WebDriver driver = new FirefoxDriver(fb, null); // or pass in a FirefoxProfile

And this fixed the problem :)

Reported by ginknee17 on 2015-01-28 15:29:52

lukeis commented 8 years ago 
The link does not work, but the code you provided looks very trivial. I do not think,
it is so easy.
In selenium firefox driver, default value is from code:
  private long timeout = SECONDS.toMillis(45);
45 seconds, so it can not work like that (since the 3 hours of waiting...).

Reported by flesnablizna on 2015-02-04 16:29:13

lukeis commented 8 years ago 
Hi I am also encountering this error. I am quite new so Selinium but I get this error
around 1.5hrs into running what happens in my case is that the  IEDriverServer.exe
crashes.

My configuration is as follows.
Windows 7 64Bit
Internet Explorer 11.0.9
C# using .NET 4.0

Reported by ricson.chua on 2015-02-12 01:01:18

lukeis commented 8 years ago 
this must be sev 1 bug

Reported by ramprasadgk on 2015-05-19 05:49:14

lukeis commented 8 years ago 
I am also facing this issue. Any pointers on how to fix this?

Reported by ruchi.sethi on 2015-06-01 17:28:33

lukeis commented 8 years ago 
I am also observing this error on windows 7 64 bit, IE 11, Java, eclipse, webdriver
2.46  and observe this issue whenever script switch back to parent window after accepting
an alert box and control comes to main window after attaching an image

Reported by jlearner.2014 on 2015-08-07 11:01:01

lukeis commented 8 years ago 
Hi, we are facing the same issue!

Firefox: 38.1.1
Selenium Version: 2.47.1
Tests startet from a jenkins node (that also serves as a selenium hub) and running
on windows machines (which are running as selenium nodes)

scenario that regulary results in the timeout problem:
Testcase starts Firefox do some gui stuff, that leads to two(!) further Firefox windows
that are opened. Trying to close the latest window, a native alert box is showing up.
Selenium is not able to close the alertbox via 

Alert alert = driver.switchTo().alert();
alert.accept();

because afterwards the driver.getWindowHandles() still logs all three windowhandles!
after that the method driver.getWindowHandle() results in the 3 hour timeout!

here the stacktrace:
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.47.1', revision: 'unknown', time: '2015-07-30 11:02:44'
System info: host: 'congstar-slave1', ip: '91.250.95.6', os.name: 'Linux', os.arch:
'amd64', os.version: '3.2.0-88-generic', java.version: '1.7.0_45'
Driver info: driver.version: EventFiringWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:589) ~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:618) ~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.RemoteWebDriver.getWindowHandle(RemoteWebDriver.java:485)
~[selenium-remote-driver-2.47.1.jar:na]
    at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) ~[na:na]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.7.0_45]
    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_45]
    at org.openqa.selenium.remote.Augmenter$CompoundHandler.intercept(Augmenter.java:191)
~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.RemoteWebDriver$$EnhancerByCGLIB$$be58ad95.getWindowHandle(<generated>)
~[cglib-nodep-2.1_3.jar:na]
    at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) ~[na:na]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.7.0_45]
    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_45]
    at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:102)
~[selenium-support-2.47.1.jar:na]
    at com.sun.proxy.$Proxy18.getWindowHandle(Unknown Source) ~[na:na]
    at org.openqa.selenium.support.events.EventFiringWebDriver.getWindowHandle(EventFiringWebDriver.java:207)
~[selenium-support-2.47.1.jar:na]
    at de.congstar.acceptancetests.common.testcases.TestCaseRule.failed(TestCaseRule.java:100)
~[classes/:na]
    at org.junit.rules.TestWatcher.failedQuietly(TestWatcher.java:84) [junit-4.11.jar:na]
    at org.junit.rules.TestWatcher.access$300(TestWatcher.java:46) [junit-4.11.jar:na]
    at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:62) [junit-4.11.jar:na]
    at org.junit.rules.RunRules.evaluate(RunRules.java:20) [junit-4.11.jar:na]
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) [junit-4.11.jar:na]
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
[junit-4.11.jar:na]
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
[junit-4.11.jar:na]
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) [junit-4.11.jar:na]
    at org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:387) [surefire-junit47-2.18.1.jar:2.18.1]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_45]
    at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_45]
    at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
Caused by: java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_45]
    at java.net.SocketInputStream.read(SocketInputStream.java:152) ~[na:1.7.0_45]
    at java.net.SocketInputStream.read(SocketInputStream.java:122) ~[na:1.7.0_45]
    at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:136)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:152)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:270)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:161)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:153)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
~[httpcore-4.3.3.jar:4.3.3]
    at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:254)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) ~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) ~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) ~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
~[httpclient-4.3.6.jar:4.3.6]
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
~[httpclient-4.3.6.jar:4.3.6]
    at org.openqa.selenium.remote.internal.ApacheHttpClient.fallBackExecute(ApacheHttpClient.java:143)
~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.internal.ApacheHttpClient.execute(ApacheHttpClient.java:89)
~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:134)
~[selenium-remote-driver-2.47.1.jar:na]
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:568) ~[selenium-remote-driver-2.47.1.jar:na]
    ... 28 common frames omitted

Interesting for me is that driver.getWindowHandles() produces no timeouts, but driver.getWindowHandle()
does!

I tried to reproduce/debug this behaviour on my local machine, but only had this effect
once, so i think this could be a timing/concurrency problem somewhere withhin selenium.

Reported by friederich.sascha on 2015-08-28 07:24:13

lukeis commented 8 years ago 
in addition to my former comment:

when trying to reproduce it locally, an NoSuchWindowException is thrown, when driver.getWindowHandle()
is called

Reported by friederich.sascha on 2015-08-28 07:27:35

lukeis commented 8 years ago 
another addition...

what we can see is, that the Future-object of the FindElemts finally get interrupted
by the socket timeout...

isnt it possible, to interrupt the Future-object after a certain time?

logfile of selenium node:
08:17:03.962 WARN - Exception thrown org.openqa.selenium.UnhandledAlertException: Unexpected
modal dialog (text: Nicht betroffene Workflows werden ³bersprungen!): Nicht betroffene
Workflows werden ³bersprungen!
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_31'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{applicationCacheEnabled=true, rotatable=false, handlesAlerts=true, databaseEnabled=true,
version=38.1.1, platform=WINDOWS, nativeEvents=false, acceptSslCerts=true, webStorageEnabled=true,
locationContextEnabled=true, browserName=firefox, takesScreenshot=true, javascriptEnabled=true,
cssSelectorsEnabled=true}]
Session ID: 48a7e557-39ab-419b-90b5-ff75e8bce12b
*** Element info: {Using=xpath, value=//input[contains(@value,'WFI nochmals freigeben')]}
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
        at org.openqa.selenium.remote.ErrorHandler.createUnhandledAlertException(ErrorHandler.java:187)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:154)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:595)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
        at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:445)
        at org.openqa.selenium.By$ByXPath.findElement(By.java:358)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:340)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:102)
        at com.sun.proxy.$Proxy1.findElement(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver.findElement(EventFiringWebDriver.java:185)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:48)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:1)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
08:17:03.965 WARN - Exception: Unexpected modal dialog (text: Nicht betroffene Workflows
werden ³bersprungen!): Nicht betroffene Workflows werden ³bersprungen!
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_31'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
Capabilities [{applicationCacheEnabled=true, rotatable=false, handlesAlerts=true, databaseEnabled=true,
version=38.1.1, platform=WINDOWS, nativeEvents=false, acceptSslCerts=true, webStorageEnabled=true,
locationContextEnabled=true, browserName=firefox, takesScreenshot=true, javascriptEnabled=true,
cssSelectorsEnabled=true}]
Session ID: 48a7e557-39ab-419b-90b5-ff75e8bce12b
*** Element info: {Using=xpath, value=//input[contains(@value,'WFI nochmals freigeben')]}
08:17:04.020 INFO - Executing: [find element: By.xpath: //input[@id='dunningState:allOrMarked:1'
and @value='2']])
11:17:04.491 ERROR - Unexpected exception during findElement org.openqa.selenium.remote.UnreachableBrowserException:
Error communicating with the remote browser. It may have died.
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_31'
Driver info: driver.version: EventFiringWebDriver
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:589)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
        at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:445)
        at org.openqa.selenium.By$ByXPath.findElement(By.java:358)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:340)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:102)
        at com.sun.proxy.$Proxy1.findElement(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver.findElement(EventFiringWebDriver.java:185)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:48)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:1)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(Unknown Source)
        at java.net.SocketInputStream.read(Unknown Source)
        at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:139)
        at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:155)
        at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:284)
        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
        at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
        at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261)
        at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165)
        at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:167)
        at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272)
        at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
        at org.openqa.selenium.remote.internal.ApacheHttpClient.fallBackExecute(ApacheHttpClient.java:143)
        at org.openqa.selenium.remote.internal.ApacheHttpClient.execute(ApacheHttpClient.java:89)
        at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:134)
        at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:170)
        at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:393)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:568)
        ... 17 more
11:17:04.510 INFO - Executing: [find element: By.xpath: //input[contains(@value,'WFI
nochmals freigeben')]])
11:17:05.138 ERROR - Unexpected exception during findElement org.openqa.selenium.NoSuchWindowException:
Window not found. The browser windowmay have been closed. Command duration or timeout:
81 milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_31'
Driver info: org.openqa.selenium.firefox.FirefoxDriverCapabilities [{applicationCacheEnabled=true,
rotatable=false, handlesAlerts=true, databaseEnabled=true, version=38.1.1, platform=WINDOWS,
nativeEvents=false, acceptSslCerts=true, webStorageEnabled=true, locationContextEnabled=true,
browserName=firefox, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: 48a7e557-39ab-419b-90b5-ff75e8bce12b
*** Element info: {Using=xpath, value=//input[contains(@value,'WFI nochmals freigeben')]}
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:595)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
        at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:445)
        at org.openqa.selenium.By$ByXPath.findElement(By.java:358)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:340)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:102)
        at com.sun.proxy.$Proxy1.findElement(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver.findElement(EventFiringWebDriver.java:185)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:48)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:1)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.openqa.selenium.NoSuchWindowException: Window not found. The browser
window may have been closed.
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'
System info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch:
'amd64', os.version: '6.1', java.version: '1.8.0_31'
Driver info: driver.version: unknown
        at <anonymous class>.nsCommandProcessor.prototype.execute(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:12711)
        at <anonymous class>.Dispatcher.executeAs/<(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9456)
        at <anonymous class>.Resource.prototype.handle(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9603)
        at <anonymous class>.Dispatcher.prototype.dispatch(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9550)
        at <anonymous class>.WebDriverServer/<.handle(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:12497)
        at <anonymous class>.createHandlerFunc/<(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:2054)
        at <anonymous class>.ServerHandler.prototype.handleResponse(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:2387)
        at <anonymous class>.Connection.prototype.process(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1223)
        at <anonymous class>.RequestReader.prototype._handleResponse(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1677)
        at <anonymous class>.RequestReader.prototype._processBody(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1525)
        at <anonymous class>.RequestReader.prototype.onInputStreamReady(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1393)
11:17:05.144 WARN - Exception thrown org.openqa.selenium.NoSuchWindowException: Window
not found. The browser windowmay have been closed. Command duration or timeout: 81
milliseconds
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'System
info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch: 'amd64',
os.version: '6.1', java.version: '1.8.0_31'
Driver info: org.openqa.selenium.firefox.FirefoxDriverCapabilities [{applicationCacheEnabled=true,
rotatable=false, handlesAlerts=true, databaseEnabled=true, version=38.1.1, platform=WINDOWS,
nativeEvents=false, acceptSslCerts=true, webStorageEnabled=true, locationContextEnabled=true,
browserName=firefox, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}]
Session ID: 48a7e557-39ab-419b-90b5-ff75e8bce12b
*** Element info: {Using=xpath, value=//input[contains(@value,'WFI nochmals freigeben')]}
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:595)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
        at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:445)
        at org.openqa.selenium.By$ByXPath.findElement(By.java:358)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:340)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver$2.invoke(EventFiringWebDriver.java:102)
        at com.sun.proxy.$Proxy1.findElement(Unknown Source)
        at org.openqa.selenium.support.events.EventFiringWebDriver.findElement(EventFiringWebDriver.java:185)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:48)
        at org.openqa.selenium.remote.server.handler.FindElement.call(FindElement.java:1)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:176)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: org.openqa.selenium.NoSuchWindowException: Window not found. The browser
window may have been closed.
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'System
info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.arch: 'amd64',
os.version: '6.1', java.version: '1.8.0_31'
Driver info: driver.version: unknown
        at <anonymousclass>.nsCommandProcessor.prototype.execute(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/command-processor.js:12711)
        at <anonymous class>.Dispatcher.executeAs/<(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9456)
        at <anonymous class>.Resource.prototype.handle(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9603)
        at <anonymous class>.Dispatcher.prototype.dispatch(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:9550)
        at <anonymous class>.WebDriverServer/<.handle(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/driver-component.js:12497)
        at <anonymous class>.createHandlerFunc/<(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:2054)
        at <anonymous class>.ServerHandler.prototype.handleResponse(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:2387)
        at <anonymous class>.Connection.prototype.process(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1223)
        at <anonymous class>.RequestReader.prototype._handleResponse(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1677)
        at <anonymous class>.RequestReader.prototype._processBody(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1525)
        at <anonymous class>.RequestReader.prototype.onInputStreamReady(file:///C:/Users/SFRIED~1/AppData/Local/Temp/anonymous1190664805323921713webdriver-profile/extensions/fxdriver@googlecode.com/components/httpd.js:1393)
11:17:05.150 WARN - Exception: Window not found. The browser window may have been closed.
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03:16'System
info: host: 'NBL10364', ip: '192.168.180.68', os.name: 'Windows 7', os.ar
ch: 'amd64', os.version: '6.1', java.version: '1.8.0_31'Driver info: driver.version:
unknown
11:22:09.609 INFO - Session c4ec068f-cc53-4783-9535-3e1bdb2eba44 deleted due toclient
timeout

logfile of selenium hub:
07:44:53.130 INFO - Launching Selenium Grid hub
2015-08-24 07:44:54.348:INFO:osjs.Server:jetty-7.x.y-SNAPSHOT
2015-08-24 07:44:54.407:INFO:osjsh.ContextHandler:started o.s.j.s.ServletContextHandler{/,null}
2015-08-24 07:44:54.417:INFO:osjs.AbstractConnector:Started SocketConnector@0.0.0.0:4444
07:44:54.419 INFO - Nodes should register to http://192.168.180.68:4444/grid/register/
07:44:54.419 INFO - Selenium Grid hub is up and running
07:45:04.280 WARN - Max instance not specified. Using default = 1 instance
07:45:04.282 INFO - Registered a node http://192.168.180.68:5555
08:14:16.505 INFO - Got a request to create a new session: Capabilities [{browserName=firefox,
version=, platform=WINDOWS, firefox_profile=UEsDBBQACAgIAMdBGEcAAAAAAAAAA...}]
08:14:16.506 INFO - Available nodes: [http://192.168.180.68:5555]
08:14:16.507 INFO - Trying to create a new session on node http://192.168.180.68:5555
08:14:16.508 INFO - Trying to create a new session on test slot {firefox_binary=C:\Program
Files (x86)\Mozilla Firefox\firefox.exe, seleniumProtocol=WebDriver,browserName=firefox,
version=4, platform=VISTA}
11:17:04.514 WARN - IOException thrown while closing Closeable.
org.seleniumhq.jetty7.io.EofException
        at org.seleniumhq.jetty7.http.HttpGenerator.flushBuffer(HttpGenerator.java:939)
        at org.seleniumhq.jetty7.server.AbstractHttpConnection.flushResponse(AbstractHttpConnection.java:612)
        at org.seleniumhq.jetty7.server.AbstractHttpConnection$Output.close(AbstractHttpConnection.java:1001)
        at com.google.common.io.Closeables.close(Closeables.java:79)
        at org.openqa.selenium.io.IOUtils.closeQuietly(IOUtils.java:45)
        at org.openqa.grid.internal.TestSession.writeRawBody(TestSession.java:440)
        at org.openqa.grid.internal.TestSession.forward(TestSession.java:266)
        at org.openqa.grid.web.servlet.handler.RequestHandler.forwardRequest(RequestHandler.java:96)
        at org.openqa.grid.web.servlet.handler.RequestHandler.process(RequestHandler.java:129)
        at org.openqa.grid.web.servlet.DriverServlet.process(DriverServlet.java:83)
        at org.openqa.grid.web.servlet.DriverServlet.doPost(DriverServlet.java:67)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.seleniumhq.jetty7.servlet.ServletHolder.handle(ServletHolder.java:565)
        at org.seleniumhq.jetty7.servlet.ServletHandler.doHandle(ServletHandler.java:479)
        at org.seleniumhq.jetty7.server.session.SessionHandler.doHandle(SessionHandler.java:225)
        at org.seleniumhq.jetty7.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
        at org.seleniumhq.jetty7.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at org.seleniumhq.jetty7.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.seleniumhq.jetty7.server.handler.ContextHandler.doScope(ContextHandler.java:965)
        at org.seleniumhq.jetty7.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.seleniumhq.jetty7.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.seleniumhq.jetty7.server.Server.handle(Server.java:349)
        at org.seleniumhq.jetty7.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452)
        at org.seleniumhq.jetty7.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)
        at org.seleniumhq.jetty7.server.AbstractHttpConnection.content(AbstractHttpConnection.java:894)
        at org.seleniumhq.jetty7.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:948)
        at org.seleniumhq.jetty7.http.HttpParser.parseNext(HttpParser.java:857)
        at org.seleniumhq.jetty7.http.HttpParser.parseAvailable(HttpParser.java:235)
        at org.seleniumhq.jetty7.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)
        at org.seleniumhq.jetty7.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)
        at org.seleniumhq.jetty7.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
        at org.seleniumhq.jetty7.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Software caused connection abort: socket write
error
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(Unknown Source)
        at java.net.SocketOutputStream.write(Unknown Source)
        at org.seleniumhq.jetty7.io.ByteArrayBuffer.writeTo(ByteArrayBuffer.java:354)
        at org.seleniumhq.jetty7.io.bio.StreamEndPoint.flush(StreamEndPoint.java:159)
        at org.seleniumhq.jetty7.http.HttpGenerator.flushBuffer(HttpGenerator.java:875)
        ... 33 more
11:17:04.523 WARN - The client is gone for session ext. key c4ec068f-cc53-4783-9
535-3e1bdb2eba44, terminating

Reported by friederich.sascha on 2015-08-28 09:33:56

lukeis commented 8 years ago

Reported by luke.semerau on 2015-09-17 17:45:11