You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 29, 2018. It is now read-only.
What steps will reproduce the problem?
1. Running enough jobs between remote webdriver and seleium-server will cause the the
following message:
What is the expected output? What do you see instead?
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(<unknown file>)
at java.net.PlainSocketImpl.connectToAddress(<unknown file>)
at java.net.PlainSocketImpl.connect(<unknown file>)
at java.net.SocksSocketImpl.connect(<unknown file>)
at java.net.Socket.connect(<unknown file>)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:133)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:211)
at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.execute(NewProfileExtensionConnection.java:125)
at org.openqa.selenium.firefox.FirefoxDriver$LazyCommandExecutor.execute(FirefoxDriver.java:340)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:336)
at org.openqa.selenium.firefox.FirefoxDriver.execute(FirefoxDriver.java:233)
at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:186)
at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:55)
Please use labels and text to provide additional information.
The issue happens *real* quick on Windows XP, and can be improved by http://support.microsoft.com/kb/196271
But even on a Linux box with over 30000 ephemeral we exhaust this.
The root-cause solution of this issue is to make keep-alives work between remote webdriver
and selenium server. There may also be a case for inspecting socket usage elesewhere
in the application.
Note that this issue *also* happens between the client and firefox, if run locally
or remotely. But this is slighlty less serious as it can be "mostly" solved by increasing
the number of ephemeral ports locally. But a single bamboo server can be used to drive
a truckload of clients, in which case 60000 sockets may be too little.
Reported by kristian.rosenvold on 2010-10-27 07:23:50
The text was updated successfully, but these errors were encountered:
Fixed in r10082, set the re-use option on the socket. Fixing keepalives would still
be nice for performance, but this fix should have impact for both client->firefox and
buildserver->selenium-server socket usage
Reported by kristian.rosenvold on 2010-10-28 11:00:15
Originally reported on Google Code with ID 923
Reported by
kristian.rosenvold
on 2010-10-27 07:23:50The text was updated successfully, but these errors were encountered: