INFO 03/23 05:19:15 o.b.p.j.h.HttpServer - Version Jetty/5.1.x
INFO 03/23 05:19:15 o.b.p.j.u.Container - Started HttpContext[/,/]
INFO 03/23 05:19:15 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:45454
INFO 03/23 05:19:15 o.b.p.j.u.Container - Started org.browsermob.proxy.jetty.jetty.Server@ee51b2c
INFO 03/23 05:19:31 o.b.p.j.u.Credential - Checking Resource aliases
INFO 03/23 05:19:32 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59703
INFO 03/23 05:19:33 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59707
INFO 03/23 05:19:34 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59711
INFO 03/23 05:19:35 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59721
INFO 03/23 05:19:36 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59723
INFO 03/23 05:19:36 o.b.p.j.h.SocketLis~ - Started SocketListener on 0.0.0.0:59725
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59721]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59721
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59707]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59707
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59711]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59711
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59725]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59725
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59723]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59723
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59703]]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:59703
INFO 03/23 05:19:40 o.b.p.j.u.ThreadedS~ - Stopping Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=45454]
INFO 03/23 05:19:40 o.b.p.j.h.SocketLis~ - Stopped SocketListener on 0.0.0.0:45454
INFO 03/23 05:19:41 o.b.p.j.u.Container - Stopped HttpContext[/,/]
INFO 03/23 05:19:41 o.b.p.j.u.Container - Stopped org.browsermob.proxy.jetty.jetty.Server@ee51b2c
I guess what you're saying is the difference is between selenium-server-standalone vs just selenium-firefox-driver + dependencies is causing the issue? If so, it might just not be something we support. The selenium-server-standalone jar is one of those "jar of jars" packages that can cause strange classpath issues sometimes. I generally avoid those kinds of uberjars unless I'm running it as a standalone process. But mixing it with other libraries can produce unexpected results.
Patrick
--
Patrick Lightbody
+1 (415) 830-5488