RE: [webdriver] Error communicating with the remote browser

[Leonardo Galani]

we kind dont need the full stack...

send the code you are using to declare the webdriver..

---

De: Kasam
Enviada em: 18/12/2012 10:35
Para: webd...@googlegroups.com
Assunto: [webdriver] Error communicating with the remote browser

2012/12/14 19:58:05.67;ERROR;(TestBatchRunner.java:582);Exception::
org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died.
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_26'
Driver info: driver.version: Driver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:493)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:502)
    at org.openqa.selenium.remote.RemoteWebDriver.quit(RemoteWebDriver.java:372)
    at com.ags.aft.webdriver.common.AFTSeleniumBase.stopSelenium(AFTSeleniumBase.java:504)
    at com.ags.aft.engine.webdriver.XAFTWebDriverEngine.tearDown(XAFTWebDriverEngine.java:209)
    at com.ags.aft.runners.TestBatchRunner.tearDown(TestBatchRunner.java:683)
    at com.ags.aft.runners.TestBatchRunner.exitTestBatchRunner(TestBatchRunner.java:843)
    at com.ags.aft.runners.TestBatchRunner.execute(TestBatchRunner.java:567)
    at com.ags.aft.main.Driver.main(Driver.java:122)
Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
    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)
    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:319)
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:297)
    at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:136)
    at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:357)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:472)

We are facing this issue on Windows XP & Window 7 , using selenium-java-2.26.0 jar
Please help out.

Thanks
Srikanth

--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To view this discussion on the web visit https://groups.google.com/d/msg/webdriver/-/2FQn_3xyiw4J.
To post to this group, send email to webd...@googlegroups.com.
To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

[Leonardo Galani]

Thats why i asked the code..
Its closing the browser and still trying to execute stuff.. (u can tell by the method tear down.. i guess he is calling quit twice...)

---

De: Debabrata Chakraborty
Enviada em: 19/12/2012 03:22
Para: webd...@googlegroups.com
Assunto: Re: [webdriver] Error communicating with the remote browser

It could also possible that browser is closed during the execution.

 

 

Thanks,

Debabrata

On Wed, Dec 19, 2012 at 7:15 AM, Krishnan Mahadevan <krishnan.ma...@gmail.com> wrote:

This error is NOT related to heap space but due to the OS running out of ports. 

I have seen this sort of issue sometime back on a Windows XP machine. 

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

On Wednesday, December 19, 2012, Mike Riley wrote:

It sounds to me like you ran out of heap space based on this error:

Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): connect

I started allocating a larger than default heap space for my node and grid servers a while back.  See if that helps.

Mike

To view this discussion on the web visit https://groups.google.com/d/msg/webdriver/-/mRyN40P5v8sJ.

To post to this group, send email to webd...@googlegroups.com.
To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

--
You received this message because you are subscribed to the Google Groups "webdriver" group.

To post to this group, send email to webd...@googlegroups.com.
To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

--
Thanks,
Debabrata

--
You received this message because you are subscribed to the Google Groups "webdriver" group.