Skip to main content

How to over come "Failed to start: SocketListener0@0.0.0.0:4444"

This is the most common error which is encountered while starting the
selenium server. The origin of this error is the fact that selenium server always
tries to listen at port 4444 by default so when following is written at command
prompt -

java -jar selenium-server.jar

The server starts running on port 4444 but if this post is already occupied
then server will fail to listen at this port and following error will be
encountered -

Failed to start: SocketListener0@0.0.0.0:4444

To over come this one can force server to listen at port any other port while
starting the selenium server as following -

java -jar selenium-server.jar -port 5555

and this will start server as following -

10:55:14.440 INFO - Java: Sun Microsystems Inc. 1.5.0_05-b05
10:55:14.440 INFO - OS: Windows XP 5.1 x86
10:55:14.456 INFO - v1.0-SNAPSHOT [1123], with Core v1.0-SNAPSHOT [2101]
10:55:14.549 INFO - Version Jetty/5.1.x
10:55:14.549 INFO - Started HttpContext[/,/]
10:55:14.549 INFO - Started HttpContext[/selenium-server,/selenium-server]
10:55:14.549 INFO - Started
HttpContext[/selenium-server/driver,/selenium-server
/driver]
10:55:14.565 INFO - Started SocketListener on 0.0.0.0:5555
10:55:14.565 INFO - Started org.mortbay.jetty.Server@e0e1c6
If same error is encountered again then keep changing port till server gets
started on a port.

You could also shut down Selenium Server using following URL in your browser -

http://localhost:4444/selenium-server/driver/?cmd=shutDownSeleniumServer

Comments

  1. Thanks, this is exactly what I needed.

    ReplyDelete
  2. Thanks Tarun now how do i stop the selenium rc server in command prompt or what is the easiest way to stop it

    ReplyDelete
  3. Thanks much it helped me

    ReplyDelete

Post a Comment

No spam only genuine comments :)

Popular posts from this blog

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro