I believe you need to use the -role switch. I have never started it
without that switch, but this looks to me as if it started up in the
hub role. Here is how I start my hub:
java -jar selenium-server-standalone.jar"-role hub -nodeTimeout 600
And here is the output you see when it starts up:
Sep 20, 2011 4:29:47 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
Sep 20, 2011 4:29:48 PM org.openqa.jetty.http.HttpServer doStart
INFO: Version Jetty/5.1.x
Sep 20, 2011 4:29:48 PM org.openqa.jetty.util.FileResource <clinit>
INFO: Checking Resource aliases
Sep 20, 2011 4:29:48 PM org.openqa.jetty.util.Container start
INFO: Started
org.openqa.jetty.jetty.servlet.WebApplicationHandler@b2a2d8
Sep 20, 2011 4:29:49 PM org.openqa.jetty.util.Container start
INFO: Started WebApplicationContext[/,/]
Sep 20, 2011 4:29:49 PM org.openqa.jetty.http.SocketListener start
INFO: Started SocketListener on
0.0.0.0:4444
Sep 20, 2011 4:29:49 PM org.openqa.jetty.util.Container start
INFO: Started org.openqa.jetty.jetty.Server@f38798
To start it up in WebDriver mode I use this:
java -jar selenium-server-standalone.jar -role webdriver -hub
http://10.0.2.208:4444/grid/register
If you are not using a Grid server you can leave off the -hub switch,
which registers it with the Grid server.
I hope that helps.
Mike