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

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

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

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.