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

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Verify email confirmation using Selenium WebDriver

Note: If you are new to java and selenium then start with selenium java training videos .   How to Verify Email Confirmation Using Selenium 4 and JavaMail (2026 Guide) Email confirmation is a critical part of most registration flows — account activation, password reset, multi-factor authentication, and onboarding. Every automation engineer eventually faces the same challenge: How do you verify an email confirmation link inside a Selenium test without making it slow and flaky? The wrong instinct is to automate Gmail's UI with Selenium. It's fragile, slow, and breaks constantly. The right approach: Use Selenium for browser automation Use JavaMail (IMAP) to read the email directly Extract the confirmation link Continue the test in Selenium Why Not Automate Gmail UI With Selenium? Automating the Gmail UI means logging in, searching, clicking a message, and parsing content from a third-party interface that changes frequently. This leads to: Flaky...

Using xPath to reach parent of an element

Note: If you are new to java and selenium then start with selenium java training videos .   I prefer css locator over xPath but there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also hig...