org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.

[lukeis]

Originally reported on Google Code with ID 4319

I am very often facing this issue.I use to execute 10/12 Test cases using Junit TestSuite,but
it fails in between somewhere and displays error-"org.openqa.selenium.remote.UnreachableBrowserException:
Error communicating with the remote browser. It may have died."I am using Selenium2
and Mozilla browser version 9.0.1.Is there any solution for this or is there any alternative?

Trace is as follows-

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:57:28'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_18'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:421)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:428)
    at org.openqa.selenium.remote.RemoteWebDriver.getPageSource(RemoteWebDriver.java:293)
    at Source_fx.ExpectedUImsg(Source_fx.java:751)
    at IssuingTransactionFeeAdd.IssuingSetupTransactionFeeToAdd(IssuingTransactionFeeAdd.java:70)
    at IssuingCardGeneration.testcase1(IssuingCardGeneration.java:39)
    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 junit.framework.TestCase.runTest(TestCase.java:168)
    at junit.framework.TestCase.runBare(TestCase.java:134)
    at junit.framework.TestResult$1.protect(TestResult.java:110)
    at junit.framework.TestResult.runProtected(TestResult.java:128)
    at junit.framework.TestResult.run(TestResult.java:113)
    at junit.framework.TestCase.run(TestCase.java:124)
    at junit.framework.TestSuite.runTest(TestSuite.java:243)
    at junit.framework.TestSuite.run(TestSuite.java:238)
    at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.apache.http.ConnectionClosedException: Premature end of Content-Length
delimited message body (expected: 39684; received: 32768
    at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178)
    at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:197)
    at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:155)
    at org.apache.http.util.EntityUtils.toByteArray(EntityUtils.java:100)
    at org.openqa.selenium.remote.HttpCommandExecutor$EntityWithEncoding.<init>(HttpCommandExecutor.java:486)
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:381)
    at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:122)
    at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:237)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:401)
    ... 24 more

Reported by ajit.choudhari on 2012-07-26 13:00:49

[lukeis]

The same problem occurs with me, usually when testing for ChromeDriver under Selenium
2.25.0, somewhere in the middle of test suite. The tests, however, continue to run
ok — only one test is failed with this error. Rerunning it results in success.

Reported by Actinate on 2012-07-26 14:00:50

[lukeis]

Reported by barancev on 2012-08-02 19:25:01

• Labels added: Component-WebDriver

[lukeis]

I'm also randomly getting this. I'm running the tests under junit on ubuntu against
firefox.  Of 30 tests 0-3 might fail, but which test, and whether any do, seems random.
 In my latest set of logs it looks like it took the tests 3 hours to timeout and realize
the browser wasn't responding.


   <error message="Error communicating with the remote browser. It may have died.
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-42-server', java.version:
'1.6.0_30'
Driver info: driver.version: RemoteWebDriver" type="org.openqa.selenium.remote.UnreachableBrowserException">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: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-42-server', java.version:
'1.6.0_30'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:467)
    at org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions$RemoteWindow.getSize(RemoteWebDriver.java:660)
    at com.perforce.test.cloud.SeleniumDriverFactory.defaultDriver(SeleniumDriverFactory.java:159)
    at com.perforce.test.cloud.SeleniumDriverFactory.getDriver(SeleniumDriverFactory.java:119)
    at com.perforce.test.cloud.tests.BaseSeleniumTestcase.setup(BaseSeleniumTestcase.java:34)
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: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.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:136)
    at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:325)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:446)
</error>

Reported by martin.phillips.100 on 2012-08-15 10:09:35

[lukeis]

same issue over here : 
chrome version 21.0.1180.83 m
chromedriver 22
selenium 2.24.1
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 15:28:49'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_25'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:467)
    at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:244)
    at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:77)
    at geb.navigator.NonEmptyNavigator.click(NonEmptyNavigator.groovy:297)
    at geb.content.TemplateDerivedPageContent.click(TemplateDerivedPageContent.groovy:105)
    at ec.europa.eures.atp.seca.scenarios.sc002.TC_SC002_MAN_SER_AVA_01.completeCommentsForChannel(TC_SC002_MAN_SER_AVA_01.groovy:44)
    at org.spockframework.util.GroovyRuntimeUtil.invokeMethod(GroovyRuntimeUtil.java:100)
    at ec.europa.eures.atp.seca.scenarios.sc002.TC_SC002_MAN_SER_AVA_01.Manage the information
of a service for Jobseekers for a service provider(TC_SC002_MAN_SER_AVA_01.groovy:171)
Caused by: org.openqa.selenium.WebDriverException: java.net.SocketException: Connection
reset
Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 15:28:49'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_25'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:75)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:446)
    ... 7 more
Caused by: java.net.SocketException: Connection reset
    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)
    ... 8 more

Reported by LAK.le.kiet on 2012-08-22 13:32:03

[lukeis]

Hi, I get the same issue.

I am using Selenium-Server-standalone-v.2.25
Error appeared with: internet explorer version: 7 platform: WINDOWS

212 2012-09-22 13:31:26   Destroying driver.
213 2012-09-22 16:31:26   Test Case viewer_1 caused the following exception:
214 2012-09-22 16:31:26    org.openqa.selenium.remote.UnreachableBrowserException:
Error communicating with the remote browser. It may have died.
215 Build info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:56:25'
216 System info: os.name: 'SunOS', os.arch: 'sparcv9', os.version: '5.10', java.version:
'1.6.0_29-rev'
217 Driver info: driver.version: RemoteWebDriver
218 2012-09-22 16:31:26   With the message:
219 2012-09-22 16:31:26    Error communicating with the remote browser. It may have
died.
220 Build info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:56:25'
221 System info: java.version: '1.6.0_29-rev'
222 Driver info: driver.version: RemoteWebDriver
223 2012-09-22 16:31:26   Stack trace: 
224 2012-09-22 16:31:26    org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:421)
225 2012-09-22 16:31:26    org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:428)
226 2012-09-22 16:31:26    org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:302)

The "Destroying driver." output is generated by a method that calls: RemoteWebDriver.quit();

As you can see it takes about 3 hours until I get the exception

I'll try to reproduce this and post further comments, if I was successful.

Reported by mu7eh7 on 2012-09-22 17:42:15

[lukeis]

Found a workaround in stackoverflow:
http://stackoverflow.com/questions/11261602/selenium-abotring-with-unreachablebrowserexception-address-already-in-use-occu
Maybe this will solve your case too.

Reported by turzait on 2012-09-23 15:26:17

[lukeis]

Hi Friends,

Even i am also facing the same issue here. I am using Selenium 2.0 version-2.25.0 and
browser firefox version -14.0.1
my code contains only few click methods nothing more than that.Please help me out to
solve this issue.

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.

Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_13'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:502)
    at org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions.deleteAllCookies(RemoteWebDriver.java:565)
    at explore.Practice.tearDown(Practice.java:36)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: org.openqa.selenium.WebDriverException: The FirefoxDriver cannot be used
after quit() was called.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version:
'1.6.0_13'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:355)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)

Reported by tramakrishna@prokarmasoftech.com on 2012-09-25 14:24:35

[lukeis]

Hi. Any updates on it?
I've got the same error, but using java with testng - my test just stoped working and
this error appeared every run.
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the
remote browser. It may have died.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version:
'1.6.0_35'
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:268)
at org.openqa.selenium.remote.RemoteWebDriver.findElementById(RemoteWebDriver.java:297)
at org.openqa.selenium.By$ById.findElement(By.java:215)
at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:260)
at allow_tests.testFirefox1_signup(allow_tests.java:135)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:76)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) 

Reported by gvozdevaira on 2012-10-03 19:24:28

[lukeis]

I think I figured out the three hours part of it.  From looking at the HttpClientFactory
in the selenium source, I found the following:

public HttpParams getHttpParams() {
    HttpParams params = new BasicHttpParams();
    HttpConnectionParams.setSoReuseaddr(params, true);
    HttpConnectionParams.setConnectionTimeout(params, 120 * 1000);
    HttpConnectionParams.setSoTimeout(params, TIMEOUT_THREE_HOURS);
    params.setIntParameter(ConnConnectionPNames.MAX_STATUS_LINE_GARBAGE, 0);
    HttpConnectionParams.setStaleCheckingEnabled(params, true);
    return params;
  }

This looks like it can be overridden if using Grid, but not when you are using basic
WebDriver.  I could be wrong on that, but it seems that way.

Three hours is a pretty long default timeout for a single command.  Is there some way
we can have more control over this?  It wouldn't address the problem completely, but
would allow a faster failure.

Reported by dan.woodward on 2012-10-03 22:27:14