Re: Issue 3000 in selenium: Getting org.openqa.selenium.WebDriverException: Error communicating with the remote browser. It may have died.

[sele...@googlecode.com]

Comment #17 on issue 3000 by santhosh...@gmail.com: Getting
org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I am also getting same error with FF 3.6 and driver version 2.16.1 is this
issue fixed or not?

[sele...@googlecode.com]

Comment #18 on issue 3000 by fdez.pe...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I have tried with Selenium version 2.19 and this issue still reproduces.

[sele...@googlecode.com]

Comment #19 on issue 3000 by ddesm...@prospectiv.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Same here. Seeing in 2.19.0. running this code snippet:
for( String voucherId : resultSet ) {
try {
element = driver.findElement(By.xpath("//div[@title='"+voucherId+"']"));
assertEquals("Verify expired voucher id is on page.",
element.getText(), voucherId);
} catch( NoSuchElementException nsee ) {
fail("Failed to ...'"+voucherId+"' on the page.");
}
}

[sele...@googlecode.com]

Comment #20 on issue 3000 by ddesm...@prospectiv.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Using Firefox Browser 10.0.1 and WebDriver:

for( String voucherId : resultSet ) {
try {
element = driver.findElement(By.xpath("//div[@title='"+voucherId+"']"));
assertEquals("Verify expired voucher id is on page.",
element.getText(), voucherId);
} catch( NoSuchElementException nsee ) {
fail("Failed to ...'"+voucherId+"' on the page.");
}
}

Here the stack trace:
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Build info: version: '2.19.0', revision: '15849', time: '2012-02-08
16:10:57'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.6.0_30'
Driver info: driver.version: RemoteWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:436)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:443)
at
org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:318)
at
org.openqa.selenium.WebDriverCommandProcessor.stop(WebDriverCommandProcessor.java:110)
at com.thoughtworks.selenium.DefaultSelenium.stop(DefaultSelenium.java:139)
at com.eversave.tests.BaseTests.tearDown(BaseTests.java:103)
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:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37)
at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
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.conn.HttpHostConnectException: Connection to
http://127.0.0.1:7055 refused
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at
org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:403)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:382)
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:122)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:236)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:416)
... 28 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
... 38 more

[sele...@googlecode.com]

Comment #21 on issue 3000 by butt...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Also happening to me with firefox 3.6 and hub version 2.19

[sele...@googlecode.com]

Comment #22 on issue 3000 by anil.sur...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

We are seeing this time and again in our nightly execution too.
Browsers: Firefox 3.6, IE 8 and IE 9

[sele...@googlecode.com]

Comment #23 on issue 3000 by volker.k...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hello,
we've just updated to 2.20.0 and still experiencing the same problem.
With 2.12.0 everything was working fine.

Could not start a new session. Possible causes are invalid address of the
remote server or browser start-up failure. Build info: version: '2.20.0',
revision: '16008', time: '2012-02-27 19:03:59' System info:
os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.26-2-xen-amd64',
java.version: '1.6.0_23' Driver info: driver.version: RemoteWebDriver

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.20.0', revision: '16008', time: '2012-02-27
19:03:59'
System info: os.name: 'Linux', os.arch: 'amd64',
os.version: '2.6.26-2-xen-amd64', java.version: '1.6.0_23'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:435)
at
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:139)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:94)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:102)
at
de.abas.eb.selenium.rule.ConfigureFirefox.loadGridDriver(ConfigureFirefox.java:54)
at
de.abas.eb.selenium.rule.ConfigureFirefox.before(ConfigureFirefox.java:33)
at de.abas.eb.selenium.rule.WithSelenium.before(WithSelenium.java:64)
at de.abas.eb.selenium.Selenium2TestBase.before(Selenium2TestBase.java:71)
Caused by: org.apache.http.ConnectionClosedException: Premature end of
Content-Length delimited message body (expected: 5767; received: 3769
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.impl.io.ContentLengthInputStream.close(ContentLengthInputStream.java:105)
at
org.apache.http.conn.BasicManagedEntity.streamClosed(BasicManagedEntity.java:152)
at
org.apache.http.conn.EofSensorInputStream.checkClose(EofSensorInputStream.java:237)
at
org.apache.http.conn.EofSensorInputStream.close(EofSensorInputStream.java:186)
at org.apache.http.util.EntityUtils.consume(EntityUtils.java:67)
at
org.openqa.selenium.remote.HttpCommandExecutor$EntityWithEncoding.<init>(HttpCommandExecutor.java:399)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:287)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:415)

[sele...@googlecode.com]

Comment #24 on issue 3000 by pavithra...@teamaol.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I also got the same error for my IE with selenium 2.18.0. But it was
because "Enable protected mode" was enabled for few of the zones under
Internet options - Security. I unchecked "Enable protected mode" for all
the zones and saved. Then, I could launch the browser successfully via grid.

[sele...@googlecode.com]

Comment #25 on issue 3000 by wasabi.n...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I get the message: Exception in thread "main"
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Could it be a problem with the proxy?

FirefoxDriver has not a method like setAutoProxy(proxy) like
HtmlUnitDriver... and when I change the FirefoxDriver to HtmlUnitDriver, I
get an error: Cannot make a static reference to the non-static method
setAutoProxy(String) from the type HtmlUnitDriver. And this error won't
dissapear!

How can I set a Proxy with the FirefoxDriver?

Greetings

Attachments:
Error.jpg 304 KB

[sele...@googlecode.com]

Comment #26 on issue 3000 by p...@hammant.org: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Given I can reproduce this at will, as far as I'm concerned it happened
after the release of 2.11 and is reproducible in 2.12 through to 2.20 today.

Hypothesis: Is it possible that code is interacting with the remote
browser too fast? Especially in terms of retry or polling style wait-fors ?

[sele...@googlecode.com]

Comment #27 on issue 3000 by kristian...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

The error message is a general error handler that simply
indicates "something" is wrong, which is illustrated by the fact that this
issue contains stacktraces from *all* the browsers, with and without grid.

The "good news" for all of the grid users is that this message will change
for 2.21, and there is a significant chance that you will be seeing a
different problem (the real one).

Since there are at least 5 distinct problems reported in this thread, this
issue is turning into an epic that will never be fixed. Please do not
report anything but ChromeDriver related problems further in this thread;
even though you are getting the same error message it is not the same
problem.

I would like to have someone confirm that it's still happening with the
latest release of chromedriver and chrome.

[sele...@googlecode.com]

Comment #28 on issue 3000 by lvskip...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I will be very interested in trying that when 2.21.0 comes out. I had
always suspected it was a generic message that was hiding the real issue.

[sele...@googlecode.com]

Comment #29 on issue 3000 by nico.sch...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

seems this message is still present in 2.21 ?!?

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Build info: version: '2.2.1', revision: '16551', time: '2012-04-11 21:42:35'

System info: os.name: 'Linux', os.arch: 'amd64',

os.version: '2.6.32.45-0.3-xen', java.version: '1.6.0_30'

[sele...@googlecode.com]

Comment #30 on issue 3000 by juky....@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

could not found any useful info with 2.21.0

Exception in thread "main"

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating
with the remote browser. It may have died.
Build info: version: '2.2.1', revision: '16551', time: '2012-04-11 21:42:35'

System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.6.8',
java.version: '1.6.0_26'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:454)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:463)
at
org.openqa.selenium.remote.RemoteWebDriver.close(RemoteWebDriver.java:326)
at com.zynga.Runner.main(Runner.java:107)

Caused by: org.apache.http.ConnectionClosedException: Premature end of

Content-Length delimited message body (expected: 209; received: 0

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:391)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:286)
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:129)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:279)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:432)
... 3 more

[sele...@googlecode.com]

Comment #31 on issue 3000 by brightpe...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

In FireFox11, i have installed 9 machine to do the client reliability test.

But there two machine of 9 failed again and again for the scoket time out
issue.

By the visual observe, the firefox11 driver not reposne because it stop
glitter.

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

Build info: version: '2.21.0', revision: '16552', time: '2012-04-11
19:09:00'
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:454)
at

org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:245)
at
org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:88)
at
com.ibm.concord.automation.appobjects.common.ConcordWebElement.sendKeys(ConcordWebElement.java:215)
at
com.ibm.concord.automation.appobjects.upper.RootDocument.sendKeysWithInterval(RootDocument.java:232)
at
com.ibm.concord.automation.tasks.LotusLiveDocument.inputText(LotusLiveDocument.java:431)
at
com.ibm.concord.automation.testcases.document.DocumentCoEditTestCase_Owner.runTest(DocumentCoEditTestCase_Owner.java:55)
at
com.ibm.concord.automation.testcases.BaseTestCase.runTestCase(BaseTestCase.java:83)
at
com.ibm.concord.automation.testcases.BaseTestCase.main(BaseTestCase.java:141)
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: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.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
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:216)
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:647)
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:303)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:282)

at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:129)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:279)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:432)

... 8 more

[sele...@googlecode.com]

Comment #32 on issue 3000 by maximmid...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

you input throws InterruptedException..

example
@AfterClass(alwaysRun = true)
public void setupAfterSuite() throws InterruptedException {
logout();
driver.close();
}

[sele...@googlecode.com]

Comment #33 on issue 3000 by bk.chock...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Seeing the UnreachableBrowserException when running v2.20 of Selenium
WebDriver on Android 2.3.3 Google APIs emulator. Was trying to run
the 'OneTest' sample code provided in the AndroidDriver page when this
happened.

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Build info: version: '2.20.0', revision: '16008', time: '2012-02-28
15:00:40'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.7.3',
java.version: '1.6.0_31'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:435)
at
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:226)
at
org.openqa.selenium.remote.RemoteWebDriver.findElementByName(RemoteWebDriver.java:275)
at org.openqa.selenium.By$ByName.findElement(By.java:292)
at
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:218)

[sele...@googlecode.com]

Comment #34 on issue 3000 by david.bu...@theautomatedtester.co.uk: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Issue 4042 has been merged into this issue.

[sele...@googlecode.com]

Comment #35 on issue 3000 by ivan.pe...@groupalia.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hello,

I have the same problem but reviewing the logs I can see that every time
that this problem occurs the session Id is duplicated.
I'm working on it, but anybody know how can I manage or review the session
id provided driver?

Many thanks

[sele...@googlecode.com]

Comment #36 on issue 3000 by tgspark...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Given that you have merged the same issue, occurring with Firefox, I assume
comments can be added that don't involve Chrome. I'm getting the same
problem on a significant portion of my tests, run from both Eclipse and
from Jenkins. Here is a log from a Jenkins test run with 2.24.1 and Firefox
11.0:
[15:07:10][ERROR][AtfTestCase] Skipping test: getLastRow
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: 'amd64', os.version: '6.1',
java.version: '1.7.0_03'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:467)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:476)
at
org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:346)
at
com.twc.mas.automation.gui.MASConductor.closeConductorGUI(MASConductor.java:174)
at com.twc.mas.automation.gui.MASConductor.dispose(MASConductor.java:206)
at com.twc.mas.automation.MASController.dispose(MASController.java:513)
at
com.twc.mas.automation.gui.screens.ProcessesScreenTest.cleanUpAfterTests(ProcessesScreenTest.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:551)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:783)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:894)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1219)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:768)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:87)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1188)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1113)
at org.testng.TestNG.run(TestNG.java:1025)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:158)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:98)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: org.openqa.selenium.WebDriverException: Session ID may not be
null
Build info: version: '2.24.1', revision: '17205', time: '2012-06-19
15:28:49'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.7.0_03'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.get(HttpCommandExecutor.java:560)
at
org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.getMethod(HttpCommandExecutor.java:544)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:281)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:446)
... 42 more

[sele...@googlecode.com]

Comment #37 on issue 3000 by sreenu.g...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi,
I have the same problem.
Pls help me to fix this issue ASAP.


Selenium version:2.21.0
OS: Windows xp
Browser: Firefox
Brower version:12.0

The following error is occured when executing the test with the below code

if(driver.getPageSource().contains(text))
{
App_log.debug(" verified text");

}
else{
App_log.debug("Failed to verify text");

}


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

Build info: version: '2.21.0', revision: '16552', time: '2012-04-11
19:09:00'

System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',
java.version: '1.6.0'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:454)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:463)
at

org.openqa.selenium.remote.RemoteWebDriver.getPageSource(RemoteWebDriver.java:322)
at com.selenium.Signup.Coupon_Amount.verifycoupon(Coupon_Amount.java:128)

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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:702)

at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:894)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1219)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:768)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:87)

at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
at org.testng.TestNG.run(TestNG.java:1022)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:109)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:202)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:173)

Caused by: org.apache.http.ConnectionClosedException: Premature end of

Content-Length delimited message body (expected: 63546; received: 61440

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:391)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:286)

at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:129)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:279)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:432)

... 27 more


Thanks,
Sreenu

[sele...@googlecode.com]

Comment #38 on issue 3000 by errajasa...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I am getting this exception when trying to access iframe. This is can be
reproduced. I can't give you sample page, only live example. Is that
acceptable?

[sele...@googlecode.com]

Comment #39 on issue 3000 by testreel...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

This occurs while accessing iframes.
WIn Xp - version2002 -Service pack 3,Browser- FF13.
The loop runs 3 to 4 times then throws error.

The sample code is :

WebDriver driver = new FirefoxDriver();
driver.get("http://timesofindia.indiatimes.com/");
driver.manage().timeouts().pageLoadTimeout(30, TimeUnit.SECONDS);
driver.manage().timeouts().implicitlyWait(20, TimeUnit.SECONDS);
List <WebElement> framelist = driver.findElements(By.tagName("iframe"));
System.out.println(framelist.size());
System.out.println("+++++++++++++++++++");
for(int i =0; i<framelist.size();i++){
driver.manage().timeouts().pageLoadTimeout(60, TimeUnit.SECONDS);
driver.manage().timeouts().implicitlyWait(40, TimeUnit.SECONDS);
driver.get("http://timesofindia.indiatimes.com/");
framelist = driver.findElements(By.tagName("iframe"));
System.out.println("Loop : "+i);
driver.switchTo().frame(i);
try{

driver.findElement(By.xpath("//input[@id='mathuserans2']")).sendKeys("66");
System.out.println("Clicked");
}catch(Throwable t){
System.out.println("Error : "+i);
}
}driver.close();
++++++++++++++++++++++++++++++++++++++
Error Message :
25
+++++++++++++++++++
Loop : 0
Error : 0
Loop : 1
Error : 1
Loop : 2
Error : 2
Loop : 3
Error : 3
Loop : 4
Error : 4
Exception in thread "main"
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

16:53:24'

System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',

java.version: '1.6.0_29'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:467)
at
org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions$RemoteTimeouts.pageLoadTimeout(RemoteWebDriver.java:636)
at tabbl.fram.main(fram.java:24)

Caused by: org.apache.http.ConnectionClosedException: Premature end of

Content-Length delimited message body (expected: 219; received: 0

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:407)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:302)
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)
... 2 more

[sele...@googlecode.com]

Comment #40 on issue 3000 by yish...@wix.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Using chromedriver v. 21.0.1180.4, I suffered from this problem very often.
Rolling back my chromedriver to version 18.0.995.0 solved this problem for
me.

[sele...@googlecode.com]

Comment #41 on issue 3000 by bkee...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I'm getting the same issue when I try to check to see if an error message
is displayed by using .isDisplayed(). After I check if the error message is
displayed I try to push a button and then it throws that exception. I'm
using FF driver 2.24.1. Using Linux and FF 14.0.1.

When I just go through the form and click the submit button without
checking for the error message it runs smoothly. If I don't get through
this soon I'll probably roll back to the latest working FF and FF driver.

Exception in thread "main"
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

17:28:14'
System info: os.name: 'Linux', os.arch: 'amd64',
os.version: '2.6.32-36-generic', java.version: '1.6.0_20'

Driver info: driver.version: RemoteWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:467)
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:476)
at
org.openqa.selenium.remote.RemoteWebDriver$RemoteNavigation.refresh(RemoteWebDriver.java:708)
at
smartbrief.CheckSignupPages.checkFirstPageSignup(CheckSignupPages.java:123)
at smartbrief.CheckSignupPages.main(CheckSignupPages.java:45)

Caused by: org.apache.http.conn.HttpHostConnectException: Connection to
http://127.0.0.1:7055 refused
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
at

org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:150)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:575)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at
org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:337)
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)

... 4 more

Caused by: java.net.ConnectException: Connection refused

at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)

at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)

... 14 more

[sele...@googlecode.com]

Comment #42 on issue 3000 by bkee...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Here is my code, sorry forgot to put it in the post. I even tried to
refresh the form and then fill the information in again and it throws the
exception right when I try to refresh the page. Had it without the refresh
and the exception would be thrown when I try to click the submit button:




driver.findElement(By.name("confirmEmail")).clear();

driver.findElement(By.name("confirmEmail")).sendKeys("te...@test.com");
boolean
error=driver.findElement(By.xpath("//div[@class='errormessage']")).isDisplayed();
System.out.println("Check 2: "+error);
// Check to see if the error message didnt get displayed.
if (error == true){
driver.close();
System.out.println("4. Error has been displayed.");
}
else{
System.out.println("4. The email address field was
right and there shouldn't have been a warning.");
}
driver.navigate().refresh();
DriverUtils.waitDuration(2);
driver.findElement(By.name("email")).clear();

driver.findElement(By.name("email")).sendKeys("gbi...@smartbrief.com");
driver.findElement(By.name("confirmEmail")).clear();

driver.findElement(By.name("confirmEmail")).sendKeys("te...@test.com");

driver.findElement(By.id("submit-button")).click();

[sele...@googlecode.com]

Comment #43 on issue 3000 by bkee...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Sorry forgot to post my code. I had it refresh the form before I click the
submit button but no luck there the exception was thrown when I tried to
refresh the page. I also had it without the refresh and the exception would
get thrown when I try to click the submit button.

driver.findElement(By.name("confirmEmail")).clear();

driver.findElement(By.name("confirmEmail")).sendKeys("te...@test.com");

error =

driver.findElement(By.xpath("//div[@class='errormessage']")).isDisplayed();
System.out.println("Check 2: "+error);
// Check to see if the error message didnt get displayed.
if (error == true){
driver.close();
System.out.println("4. Error has been displayed.");
}
else{
System.out.println("4. The email address field was
right and there shouldn't have been a warning.");
}
driver.navigate().refresh();
DriverUtils.waitDuration(2);
driver.findElement(By.name("email")).clear();

driver.findElement(By.name("email")).sendKeys("te...@test.com");

[sele...@googlecode.com]

Comment #44 on issue 3000 by sabari....@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi Team,

Even am facing this issue when I execute the test in remote node, when the
same test is executed in the local machine it gets executed successfully.

I could see the status of this issue is "Needs Clarification".

Could you please let me know what is required so that I can do the needful.

Cheers,
Sabarivasan M

[sele...@googlecode.com]

Comment #45 on issue 3000 by sabari....@gmail.com: Getting

[sele...@googlecode.com]

Comment #46 on issue 3000 by detronizator: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Here at Neustar we have suddenly started to see this too.
Unfortunately I can't figure out what we do wrong: we haven't changed
anything of the way we use Selenium in our code base recently (next release
we move to 2.25).

I'll see if I can fetch a customer script and map it to the specific
Selenium calls we do.

[sele...@googlecode.com]

Comment #47 on issue 3000 by jstec...@steckel-schneider.de: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Workaround to avoid the UnreachableBrowserException with Firefox when
switching to an iframe (see issue #4042 for further documentation):

The WebDriver-Firefox extension seems to crash after WebDriver switched to
an iframe while the iframe's document is still loading. As a workaround one
can employ a JavaScript check that tests for some arbitrary content of the
iframe's document. The WebDriver switchTo() will only be executed after
this JavaScript check has been succesfully passed. This will prevent
WebDriver from switching to an iframe while the iframe's document is still
loading.

Sample script: http://gist.github.com/3742281

Same script without JavaScript check, thus randomly resulting in an
UnreachableBrowserException: http://gist.github.com/2883391

[sele...@googlecode.com]

Comment #48 on issue 3000 by gpapadak...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

With selenium-server-standalone-2.21.0.jar using Firefox ESR (10.0.7)
version the exception is sporadic but still exists in some cases.

[sele...@googlecode.com]

Comment #49 on issue 3000 by luke.ke...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Want to mention a workaround that has made a great improvement for my
tests. Typically, I get this error on any browser at the time of
initialization and not upon searching for elements nor executing javascript.

What I do is catch the exception and simply try again. The second attempt
has a 99% success rate, meaning it solves this issue almost every time. A
very simplified example of my code:

WebDriver driver;
int tries = 0;

main(){
start();
}

start(){
tries++;
try{
driver = new FirefoxDriver();
}
catch (Exception e){
if (tries == 1){
start();
}
else{
System.out.println("Alread tried twice");
}
}
}

I don't expect this to help every scenario that throws this error, but in
the case of initializing webdriver which is mostly where I see the
exception, this may be of use if haven't tried it.

[sele...@googlecode.com]

Comment #50 on issue 3000 by flys...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Still, in 2.26 , got the same issue.

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

Build info: version: '2.26.0', revision: '18041', time: '2012-11-01
19:33:38'
System info: os.name: 'Windows 2003', os.arch: 'x86', os.version: '5.2',
java.version: '1.6.0_37'
Driver info: driver.version: EventFiringWebDriver
Command duration or timeout: 1.41 seconds
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18
21:09:54'
System info: os.name: 'Windows 2003', os.arch: 'x86', os.version: '5.2',

java.version: '1.6.0_26'
Driver info: driver.version: RemoteWebDriver

Session ID: 1352316338639
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:188)
at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:498)
at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:242)
at com.lad.service.util.WishWorker.getSubjectDetail(WishWorker.java:93)
at
com.lad.service.util.WishWorker.loadPagesFrom3rdParty(WishWorker.java:392)
at com.lad.service.util.WishWorker.processWishList(WishWorker.java:451)
at com.lad.service.util.WishWorker.run(WishWorker.java:415)
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException:

Error communicating with the remote browser. It may have died.

Build info: version: '2.26.0', revision: '18041', time: '2012-11-01
19:33:38'
System info: os.name: 'Windows 2003', os.arch: 'x86', os.version: '5.2',
java.version: '1.6.0_37'
Driver info: driver.version: EventFiringWebDriver
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18
21:09:54'
System info: os.name: 'Windows 2003', os.arch: 'x86', os.version: '5.2',
java.version: '1.6.0_26'
Driver info: driver.version: EventFiringWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:526)
at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:275)
at sun.reflect.GeneratedMethodAccessor105.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:101)
at $Proxy1.get(Unknown Source)
at
org.openqa.selenium.support.events.EventFiringWebDriver.get(EventFiringWebDriver.java:155)
at
org.openqa.selenium.remote.server.handler.ChangeUrl.call(ChangeUrl.java:38)
at
org.openqa.selenium.remote.server.handler.ChangeUrl.call(ChangeUrl.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at
org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:150)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

[sele...@googlecode.com]

Comment #51 on issue 3000 by praneeth...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi
Iam running the tests in IE browser with selenium the latest jar
selenium-standalone2.26.jar and IEserver.exe(2.26.2). getting the following
error

Error communicating with the remote browser. It may have died. Build info:
version: '2.26.0', revision: '18041', time: '2012-11-01 19:33:38' System

info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',
java.version: '1.7.0-ea' Driver info: driver.version: RemoteWebDriver
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:526)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:535)
at
org.openqa.selenium.remote.RemoteExecuteMethod.execute(RemoteExecuteMethod.java:32)
at
org.openqa.selenium.remote.AddTakesScreenshot$1.invoke(AddTakesScreenshot.java:36)
at
org.openqa.selenium.remote.Augmenter$CompoundHandler.intercept(Augmenter.java:286)
at
org.openqa.selenium.remote.RemoteWebDriver$$EnhancerByCGLIB$$6c65f422.getScreenshotAs(<generated>)
at com.socialtwist.taf.selenium.TafSelenium.screenShot(TafSelenium.java:993)
at
com.socialtwist.taf.testnghelpers.CustomTestListener.afterInvocation(CustomTestListener.java:36)
at
org.testng.internal.invokers.InvokedMethodListenerInvoker$InvokeAfterInvocationWithoutContextStrategy.callMethod(InvokedMethodListenerInvoker.java:100)
at
org.testng.internal.invokers.InvokedMethodListenerInvoker.invokeListener(InvokedMethodListenerInvoker.java:62)
at org.testng.internal.Invoker.runInvokedMethodListeners(Invoker.java:619)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:777)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)

at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)

at org.testng.TestRunner.privateRun(TestRunner.java:767)

at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)

at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1047)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:568)
at java.lang.Thread.run(Thread.java:619)
1 lines not shown

Caused by Session ID may not be null Build info: version: '2.26.0',

revision: '18041', time: '2012-11-01 19:33:38' System info:

os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1',
java.version: '1.7.0-ea' Driver info: driver.version: RemoteWebDriver
org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.get(HttpCommandExecutor.java:570)
at
org.openqa.selenium.remote.HttpCommandExecutor$CommandInfo.getMethod(HttpCommandExecutor.java:554)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:284)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:505)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:535)
at
org.openqa.selenium.remote.RemoteExecuteMethod.execute(RemoteExecuteMethod.java:32)
at
org.openqa.selenium.remote.AddTakesScreenshot$1.invoke(AddTakesScreenshot.java:36)
at
org.openqa.selenium.remote.Augmenter$CompoundHandler.intercept(Augmenter.java:286)
at
org.openqa.selenium.remote.RemoteWebDriver$$EnhancerByCGLIB$$6c65f422.getScreenshotAs(<generated>)
at com.socialtwist.taf.selenium.TafSelenium.screenShot(TafSelenium.java:993)
at
com.socialtwist.taf.testnghelpers.CustomTestListener.afterInvocation(CustomTestListener.java:36)
at
org.testng.internal.invokers.InvokedMethodListenerInvoker$InvokeAfterInvocationWithoutContextStrategy.callMethod(InvokedMethodListenerInvoker.java:100)
at
org.testng.internal.invokers.InvokedMethodListenerInvoker.invokeListener(InvokedMethodListenerInvoker.java:62)
at org.testng.internal.Invoker.runInvokedMethodListeners(Invoker.java:619)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:777)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)

at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)

at org.testng.TestRunner.privateRun(TestRunner.java:767)

at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)

at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1047)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:568)
at java.lang.Thread.run(Thread.java:619)
1 lines not shown

[sele...@googlecode.com]

Comment #52 on issue 3000 by praneeth...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

iam using grid2 in my test environment

[sele...@googlecode.com]

Comment #53 on issue 3000 by miriam....@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi,

I see the following error when using the FirefoxDriver.
Selenium version:2.28.0
Firefox version:17.0

Error:

Error communicating with the remote browser. It may have died.

Build info: version: '2.28.0', revision: '18309', time: '2012-12-11
20:21:45'
System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64',
os.version: '6.1', java.version: '1.7.0_01'

When does the error occur:
The tests are run in parallel and when the tests in a thread are complete,
the quit() method given below is called in order to close the open browsers.
When trying to execute driver.quit(), the error is thrown - at times.

public static void quit() {
try {
if (driver != null) {
driver.quit();
}
} catch (Exception e) {
System.out.println(e.getMessage());
}
driver = null;
}

This used to work fine with Firefox 10 and Selenium 2.20.

Are there any updates/solutions for this issue?
Thanks!

[sele...@googlecode.com]

Comment #54 on issue 3000 by justin.g...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Here is another test case to consistently reproduce this exception via
another means -
http://code.google.com/p/selenium/issues/detail?id=4977&sort=-id%20-stars&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary

[sele...@googlecode.com]

Comment #55 on issue 3000 by david.ps...@messe-muenchen.de: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

you may try increasing the default maximum number of ephemeral TCP ports as
written here: http://support.microsoft.com/kb/196271/en-us

[sele...@googlecode.com]

Comment #56 on issue 3000 by psiuk.da...@gmail.com: Getting

[sele...@googlecode.com]

Comment #57 on issue 3000 by srajeshk...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Below link will be helpful to avoid this issue,

http://ipswitchft.force.com/kb/articles/FAQ/How-do-I-tune-my-Windows-TCP-stack-to-avoid-running-out-of-client-ports-1307565971362

[sele...@googlecode.com]

Comment #58 on issue 3000 by Aparna.R...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I am also getting when I am trying to launch testng suite.
single test is running successfully but running into batch mode giving
following error:

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: 'amd64', os.version: '6.1',
java.version: '1.7.0'

Driver info: driver.version: RemoteWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
at

org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:307)
at
org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:404)
at org.openqa.selenium.By$ByXPath.findElement(By.java:344)
at
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:299)
at selenium.ElementSelenium.isElementPresent(ElementSelenium.java:94)
at selenium.ElementSelenium.waitForWindowToLoad(ElementSelenium.java:114)
at selenium.ElementSelenium.waitForWindowToLoad(ElementSelenium.java:139)
at selenium.ElementSelenium.click(ElementSelenium.java:184)
at
simmanager.enterprise.workspace.AdministrationTabElement.selectSecondLevelTab(AdministrationTabElement.java:43)
at
simmanager.enterprise.workspace.AdministrationTabElement.projects(AdministrationTabElement.java:64)
at quickLook.NewStudy.testNewStudy(NewStudy.java:53)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)

at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at

org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:128)

at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)

at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)

at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1203)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1128)
at org.testng.TestNG.run(TestNG.java:1036)
at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)

Caused by: org.apache.http.conn.HttpHostConnectException: Connection to
http://127.0.0.1:7055 refused
at

org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190)
at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
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)
... 35 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:127)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
... 45 more


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[sele...@googlecode.com]

Comment #59 on issue 3000 by arran.hu...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

And what version of Firefox?

[sele...@googlecode.com]

Comment #60 on issue 3000 by skyeye1...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I met this issue one week, and it did not work on the latest build
2.31.0.Could somebody solved it? thanks a lot.

[sele...@googlecode.com]

Comment #61 on issue 3000 by justin.g...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Note that I was able to get, and duplicate this error. Info on duplication
can be found here:
https://code.google.com/p/selenium/issues/detail?can=2&start=100&num=100&q=&colspec=ID%20Stars%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=-id&id=4977

Also note that I was able to recently resolve this problem by updating my
httpcore dependency to 4.2.2

[sele...@googlecode.com]

Comment #62 on issue 3000 by eminemhe...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

I'm runing a 24 hour long run using WebDriver on firefox 19, and I can
ALWAYS meet this issue.
How long after long run will this issue reproduce is uncertain. The short
one took round 1 hour and longest once took 20 hours, but never can last
for 24 hours.
I'm using Java, Firefox 19 and Selenium 2.3.0

--------------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 logs------------------------
Mar 27, 2013 6:51:41 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 6:51:41 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executed: [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["a"]}]
Mar 27, 2013 6:51:41 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:41 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:42 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executing: sendKeysToElement [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2,
sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["d"]}]
Mar 27, 2013 6:51:42 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executed: [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":["d"]}]
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":[" "]}]
Mar 27, 2013 6:51:42 PM org.openqa.selenium.remote.RemoteWebDriver log
OFF: Executed: [7d8bbca4-f534-4a31-a3e6-6495d9cc90b2, sendKeysToElement
{"id":"{37d33ca1-58f1-4511-abc7-aa5636ed9749}","value":[" "]}]
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

The test scenario is calling sendKeys iteratively to keep entering text
into a text editor, about 3-4 character per second. Judged by the log, 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.


Besides, comment 57 is not working for me. I'm pretty sure this is not
relative with TCP port limit. I've set my TCP port limit to 65534 but still
not work.


-----------------below is my Java code snippet----------------
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) + "");
Thread.sleep(100);
} catch (StaleElementReferenceException e) {
rootdriver
.logWarning("StaleElementReferenceException occured while sendKyes:"
+ keys.charAt(i) + ":" + e.getMessage());
return i;
}
}
return keys.length();

[sele...@googlecode.com]

Comment #63 on issue 3000 by m42...@googlemail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi,

we encountered this problem with different Selenium and Firefox versions.
Also with Selenium 2.31.0 and Firefox 19.0.2. Our setup is a Windows 2003
Server with a Selenium hub and one Selenium node running on the same
machine.

After increasing
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort
to 15000 (decimal) and restarting the machine the problem no longer
occurred. A big thanks to #c56 and #c57!

After increasing we checked the tcp connections with tcpview
http://technet.microsoft.com/de-de/sysinternals/bb897437.aspx and at the
peek we had over 6000 connections in TIME_WAIT state.

[sele...@googlecode.com]

Comment #64 on issue 3000 by sag...@trainologic.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi,

I'm using Selenium 2.29.0 + Chrome, MaxUserPort = 65534(decimal)and still
encounter this issue

Regards,

Sagiv

[sele...@googlecode.com]

Comment #65 on issue 3000 by arran.hu...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

@64, what version of Chrome + ChromeDriver? This is essential to know
before going off on a debugging trail.

[sele...@googlecode.com]

Comment #66 on issue 3000 by manncho...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi, I am using selenium server 2.33 and browser is chrome27, i still
getting the same issue.. pls help.

Thanks

[sele...@googlecode.com]

Comment #67 on issue 3000 by malecspa...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi,

We had faced with same Selenium Grid behavior on Linux running more than 5
PhantomJs nodes on selenium hub sever version 2.33.0.

[sele...@googlecode.com]

Comment #68 on issue 3000 by malecspa...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

#67, Problem appears only if hub and nodes is running on same machine.

[sele...@googlecode.com]

Comment #69 on issue 3000 by dstarche...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

2malecspa: I have the same issue in IE (Win 7), Grid and nodes are on
different PCs.

[sele...@googlecode.com]

Updates:
Status: WontFix

Comment #70 on issue 3000 by barancev: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Closing the issue because it is related to chromedriver1 and is not actual
anymore.

If you experience a similar problem with chromedriver2 please raise a new
issue on the chromedriver tracker [1]

If you experience a similar problem with some other browser please raise a
new issue and try to provide an executable scenario and a sample page to
reproduce the issue.

[1] https://code.google.com/p/chromedriver/issues/list

[sele...@googlecode.com]

Comment #71 on issue 3000 by soukaina...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Exception in thread "main" org.openqa.selenium.WebDriverException: Unable
to bind to locking port 7054 within 45000 ms

Build info: version: '2.25.0', revision: '17482', time: '2012-07-18

22:18:01'

System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',

java.version: '1.6.0_27'
Driver info: driver.version: FirefoxDriver
at org.openqa.selenium.internal.SocketLock.lock(SocketLock.java:94)
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:73)
at
org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:245)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:109)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:178)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:174)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:92)
at org.openqa.selenium.example.GoogleSuggest.main(GoogleSuggest.java:19)

[sele...@googlecode.com]

Comment #72 on issue 3000 by Skampil...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

13:13:21.220 INFO - Launching Embedded Internet Explorer...
13:13:21.549 ERROR - Failed to start new browser session, shutdown browser
and c
lear all session data
org.openqa.selenium.WebDriverException: Failed to create the process: 193
Build info: version: '2.37.0', revision: 'a7c61cb', time: '2013-10-18
17:14:00'
System info: host: 'rin-vmseleniumqs', ip: '10.98.180.160',
os.name: 'Windows 7'
, os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_37'
Driver info: driver.version: unknown
at
org.openqa.selenium.os.WindowsProcessGroup.executeAsync(WindowsProces
sGroup.java:141)
at
org.openqa.selenium.server.browserlaunchers.HTABrowserLauncher.launch
(HTABrowserLauncher.java:86)
at
org.openqa.selenium.server.browserlaunchers.HTABrowserLauncher.launch
RemoteSession(HTABrowserLauncher.java:170)
at
org.openqa.selenium.server.browserlaunchers.InternetExplorerLauncher.
launchRemoteSession(InternetExplorerLauncher.java:85)
at
org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSessi
on(BrowserSessionFactory.java:400)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:144)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession
(BrowserSessionFactory.java:105)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse
rSession(SeleniumDriverResourceHandler.java:809)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se
leniumDriverResourceHandler.java:435)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman
dRequest(SeleniumDriverResourceHandler.java:405)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen
iumDriverResourceHandler.java:151)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1526)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1479)
at org.openqa.jetty.http.HttpServer.service(HttpServer.java:914)
at
org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)

at
org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:9
86)
at
org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
at
org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.
java:243)
at
org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
at
org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
13:13:21.570 WARN - Embedded iexplore seems to have ended on its own (did
we kil
l the real browser???)
13:13:21.574 INFO - Got result: Failed to start new browser session:
org.openqa.
selenium.server.RemoteCommandException: Error while launching browser on
session
null


I ve got this problem

[sele...@googlecode.com]

Comment #73 on issue 3000 by jdmesalo...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Hi, i have the same problem. When i run the test directly from eclipse
works fine, but to generate a runable jar file, failed:


org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Build info: version: '2.33.0',
revision: '4ecaf82108b2a6cc6f006aae81961236eba93358', time: '2013-05-22
12:00:17'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.7.0_25'

Driver info: driver.version: RemoteWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:569)
at
org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:423)
at
com.pagosonline.ppp4.web.tests.gateway.firefox.ScAutPayuExchangeRateNotFound.tearDown(

See later.

[sele...@googlecode.com]

Comment #74 on issue 3000 by mihai.ra...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

If you're running your tests on a Virtualbox VM with a NAT network
interface, switch to Bridged and see if that helps...

[sele...@googlecode.com]

Comment #75 on issue 3000 by info.bha...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

Selenium WebDriver with chrome
issue(org.openqa.selenium.remote.UnreachableBrowserException) solution
Exception in thread "main"
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.35.0', revision: '8df0c6b', time: '2013-08-12
15:43:19'

System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',

java.version: '1.7.0_40'
Driver info: driver.version: ChromeDriver



if you are getting above problem, go to the chromedriver.exe location and
try to execute the exe. if you are able to execute the exe then below code
will work..othere wise it will be permission issue to the chromedriver
folder. chnage the folder location or provide the permission to the folder
and double click on chromedriver.exe.

Solution:-


System.setProperty("webdriver.chrome.driver", "C:/Driver/chromedriver.exe");
System.out.println(System.getProperty("webdriver.chrome.driver"));

WebDriver driver3 = new ChromeDriver();

[sele...@googlecode.com]

Comment #76 on issue 3000 by prasan....@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

import org.openqa.selenium.By;
import org.openqa.selenium.android.AndroidDriver;
public class Home {
public static void main(String args[])throws Exception
{
AndroidDriver ad=new AndroidDriver();
System.out.println("Started");
ad.get("http://www.gmail.com");
System.out.println("Application Title"+ ad.getTitle());
Thread.sleep(2000);
ad.findElement(By.name("Email")).sendKeys("type your email");
ad.findElement(By.name("Passwd")).sendKeys("type password");
ad.findElement(By.name("signIn")).click();
System.out.println("Opened");
ad.close();
}
}
get error

Exception in thread "main"
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: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'admin2-PC', ip: '192.168.1.102', os.name: 'Windows 7',
os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_51'
Driver info: driver.version: AndroidDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
at
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:216)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:111)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:129)
at org.openqa.selenium.android.AndroidDriver.<init>(AndroidDriver.java:81)
at org.openqa.selenium.android.AndroidDriver.<init>(AndroidDriver.java:65)
at Home.main(Home.java:6)

Caused by: org.apache.http.conn.HttpHostConnectException: Connection to

http://localhost:8080 refused

at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:190)
at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)

at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
at
org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:527)
... 6 more

Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:127)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)

... 14 more
your help is more appriciated

[sele...@googlecode.com]

Comment #77 on issue 3000 by dejan999...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
http://code.google.com/p/selenium/issues/detail?id=3000

The problem is that you have hanging driver. Go to task list on machine
where you ran test and delete driver that hangs and repeat the process. Why
does it happen? Sometimes you start a test, then you stop it, before you
quit driver. It might cause driver to be
still alive and you try to run new test with new driver and they collide.

[sele...@googlecode.com]

Comment #78 on issue 3000 by Rashmi96...@gmail.com: Getting

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

https://code.google.com/p/selenium/issues/detail?id=3000

I am facing the same issue. The scripts are working fine when i run them
individually but When run them as suite, after running around 10 to 12 test
scripts, scripts will start skipping by throwing the following exception. I
m running on IE8

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating

with the remote browser. It may have died.

Build info: version: &apos;2.42.0&apos;, revision:
&apos;5e824302019c86eae9c8c3ca9155e7307b410cf8&apos;, time:
&apos;2014-05-24 09:48:41&apos;
System info: host: &apos;DELL-PC&apos;, ip: &apos;192.168.27.95&apos;,
os.name: &apos;Windows 7&apos;, os.arch: &apos;amd64&apos;, os.version:
&apos;6.1&apos;, java.version: &apos;1.7.0_67&apos;

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:590)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:611)
at
org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions.deleteAllCookies(RemoteWebDriver.java:682)
at lib.Configuration.closeBrowser(Configuration.java:49)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at

org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:786)

at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at

org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)

at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)

at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)

at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)

Caused by: org.openqa.selenium.WebDriverException:
java.net.SocketException: Permission denied: connect
Build info: version: &apos;2.42.0&apos;, revision:
&apos;5e824302019c86eae9c8c3ca9155e7307b410cf8&apos;, time:
&apos;2014-05-24 09:48:41&apos;
System info: host: &apos;DELL-PC&apos;, ip: &apos;192.168.27.95&apos;,
os.name: &apos;Windows 7&apos;, os.arch: &apos;amd64&apos;, os.version:
&apos;6.1&apos;, java.version: &apos;1.7.0_67&apos;

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:569)
... 28 more
Caused by: java.net.SocketException: Permission denied: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)

at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at

org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
at
org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:118)
at
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
at
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85)
at
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
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:204)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:173)
at
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:66)
... 29 more

[sele...@googlecode.com]

Comment #79 on issue 3000 by salamabd...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

The below is my simple code:

import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.os.WindowsUtils;

public class Openbrowser {
public static void main(String[] args) {
FirefoxDriver dr1=new FirefoxDriver();
dr1.get("http://google.com");
}
}

Output:

The Google page is opened in firefox browser, then within sec it is closing.

The following error is thrown in Eclipse:

Exception in thread "main"

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

Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23
20:03:00'
System info: host: 'ADMINIB-N6374LI', ip: '9.121.26.74', os.name: 'Windows
7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_31'

Driver info: driver.version: RemoteWebDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:593)
at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:304)
at Openbrowser.main(Openbrowser.java:7)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to
127.0.0.1:7055 [/127.0.0.1] failed: Connection refused: connect
at
org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)
at
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)

at
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)

at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)

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:233)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:184)
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:572)
... 2 more

Caused by: java.net.ConnectException: Connection refused: connect

at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)

at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at
org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
at

org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:123)
... 16 more

[sele...@googlecode.com]

Comment #80 on issue 3000 by rjomos...@freelancer.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

Hi,
Do we have a resolution for this? if we do, which version of selenium is it?

[sele...@googlecode.com]

Comment #81 on issue 3000 by rjomos...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

Do we have a resolution for this? If we do, which version of selenium is it?

[sele...@googlecode.com]

Comment #82 on issue 3000 by vkat...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

I was also getting the same error, I used below script, you may use work
around as

driver.close();
WebDriver driver1 = new FirefoxDriver();
driver=driver1;
driver1=null;
driver.get("https://slc07dag.us.oracle.com:4473/em");

[sele...@googlecode.com]

Comment #83 on issue 3000 by vkat...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

I was also getting the same error, I used below script, you may use work
around as

driver.close();
WebDriver driver1 = new FirefoxDriver();
driver=driver1;
driver1=null;

driver.get("url");

[sele...@googlecode.com]

Comment #84 on issue 3000 by megha2...@gmail.com: Getting

org.openqa.selenium.WebDriverException: Error communicating with the remote
browser. It may have died.
https://code.google.com/p/selenium/issues/detail?id=3000

hi

i am getting below error for my code:

Exception in thread "main" org.openqa.selenium.WebDriverException: Cannot
find firefox binary in PATH. Make sure firefox is installed. OS appears to
be: XP

Build info: version: '2.25.0', revision: '17482', time: '2012-07-18

21:09:54'
System info: os.name: 'Windows 8.1', os.arch: 'amd64', os.version: '6.3',
java.version: '1.8.0_51'

Driver info: driver.version: FirefoxDriver
at

org.openqa.selenium.firefox.internal.Executable.<init>(Executable.java:70)
at
org.openqa.selenium.firefox.FirefoxBinary.<init>(FirefoxBinary.java:56)
at
org.openqa.selenium.firefox.FirefoxBinary.<init>(FirefoxBinary.java:52)

at
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:92)

at RunApplication.main(RunApplication.java:14)


code used is :

import java.io.File;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxBinary;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.firefox.FirefoxProfile;


public class RunApplication {

public static void main(String[] args) {

System.out.println("Hello");

WebDriver driver = new FirefoxDriver();