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

6 views
Skip to first unread message

sele...@googlecode.com

unread,
Jun 17, 2014, 4:13:18 AM6/17/14
to selenium-develope...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Status-Untriaged

New issue 7498 by bansal.v...@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=7498

Hi,

We get the below error very frequently while we execute 20-25 scripts in
one go using CI generally.

Could you please let us know the pointer to this issue.

Error communicating with the remote browser. It may have died. Build info:
version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:54:28' System
info: host: 'wvxptdnci', ip: '10.151.58.4', os.name: 'Windows XP',
os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_17' Driver info:
driver.version: RemoteWebDriver

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating
with the remote browser. It may have died.
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19
20:54:28'
System info: host: 'wvxptdnci', ip: '10.151.58.4', os.name: 'Windows XP',
os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_17'
Driver info: driver.version: RemoteWebDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:567)
at
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:326)
at
org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:423)
at org.openqa.selenium.By$ByXPath.findElement(By.java:357)
at
org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:318)
at
com.axway.webliv.tests.MetaData.VerifyMetadataBinaryTest.checkTypeOfFile(VerifyMetadataBinaryTest.java:788)
at
com.axway.webliv.tests.MetaData.VerifyMetadataBinaryTest.testVerifyMetadataBinary(VerifyMetadataBinaryTest.java:403)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:160)
at
org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:84)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:273)
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
at
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)
at
org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283)
at
org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251)
at
org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:223)
at
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
at
org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at
org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298)
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:165)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:363)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:546)
Error communicating with the remote browser. It may have died. Build info:
version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19 20:54:28' System
info: host: 'wvxptdnci', ip: '10.151.58.4', os.name: 'Windows XP',
os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_17' Driver info:
driver.version: FirefoxDriver

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating
with the remote browser. It may have died.
Build info: version: '2.40.0', revision: 'fbe29a9', time: '2014-02-19
20:54:28'
System info: host: 'wvxptdnci', ip: '10.151.58.4', os.name: 'Windows XP',
os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_17'
Driver info: driver.version: FirefoxDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:567)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:588)
at
org.openqa.selenium.firefox.FirefoxDriver.getScreenshotAs(FirefoxDriver.java:324)
at com.axway.webliv.utilities.tools.Tools.captureScreenshot(Tools.java:1149)
at
com.axway.webliv.tests.MetaData.VerifyMetadataBinaryTest.tearDown(VerifyMetadataBinaryTest.java:1004)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:160)
at
org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:84)
at
org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:273)
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140)
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
at
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)
at
org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283)
at
org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251)
at
org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:223)
at
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
at
org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at
org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298)
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:165)
at
org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:363)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:546)

Thanks,
Vikas


--
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

unread,
Jun 17, 2014, 6:36:58 AM6/17/14
to selenium-develope...@googlegroups.com
Updates:
Status: Invalid

Comment #1 on issue 7498 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=7498

Non-actionable, there is no info to reproduce the issue.

sele...@googlecode.com

unread,
Jun 17, 2014, 9:24:14 AM6/17/14
to selenium-develope...@googlegroups.com

Comment #2 on issue 7498 by bansal.v...@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=7498

This is a generic issue happens randomly while execute the test suite using
CI however same scripts may work next time without any issue.
Thanks

sele...@googlecode.com

unread,
Jun 17, 2014, 9:25:15 AM6/17/14
to selenium-develope...@googlegroups.com

Comment #3 on issue 7498 by bansal.v...@gmail.com: Getting

sele...@googlecode.com

unread,
Jun 17, 2014, 10:00:18 AM6/17/14
to selenium-develope...@googlegroups.com

Comment #4 on issue 7498 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=7498

There is no reason to keep it open as it is non-actionable unless you can
provide enough info to reproduce it.
Reply all
Reply to author
Forward
0 new messages