Jetty takes a long time to start after running webdriver-manager start

[Lee Boynton]

Hi

I'm relatively new to selenium and have been using protractor to run some tests on my local machine where it works fine. I'm trying to run them now on a headless Chrome instance inside a virtual frame buffer, on a server. When I run webdriver-manager start, which runs "java selenium-server-standalone-2.45.0.jar", it takes a long time for Jetty to start listening:

$ ./node_modules/.bin/webdriver-manager start

seleniumProcess.pid: 7909

18:55:27.979 INFO - Launching a standalone server

Setting system property webdriver.chrome.driver to /home/lee/mycode/node_modules/protractor/selenium/chromedriver

18:55:28.108 INFO - Java: Oracle Corporation 24.79-b02

18:55:28.109 INFO - OS: Linux 3.13.0-57-generic amd64

18:55:28.163 INFO - v2.45.0, with Core v2.45.0. Built from revision 5017cb8

18:55:28.416 INFO - Default driver org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{platform=WINDOWS, ensureCleanSession=true, browserName=internet explorer, version=}] does not match with current platform: LINUX

18:55:28.459 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub

18:55:28.461 INFO - Version Jetty/5.1.x

18:55:28.462 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]

18:55:28.467 INFO - Started HttpContext[/selenium-server,/selenium-server]

18:55:28.467 INFO - Started HttpContext[/,/]

19:37:00.769 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@69d5ee81

19:37:00.770 INFO - Started HttpContext[/wd,/wd]

19:37:00.779 INFO - Started SocketListener on 0.0.0.0:4444

19:37:00.782 INFO - Started org.openqa.jetty.jetty.Server@39b5bd69

19:58:42.895 INFO - Executing: [new session: Capabilities [{count=1, browserName=chrome}]])

19:58:42.929 INFO - Creating a new session for Capabilities [{count=1, browserName=chrome}]

Starting ChromeDriver 2.15.322448 (52179c1b310fec1797c81ea9a20326839860b7d3) on port 14762

Only local connections are allowed.

...

As you can see, it doesn't start Jetty until 19:37, 42 minutes later. I was banging my head against this problem for a while, until I left it running and came back to find it had started Jetty. Before it gets to this stage I get a connection refused message when trying to connect to http://127.0.0.1:4444/wd/hub.

Is there any way to get log messages about what it's doing?

Thanks.

[Krishnan Mahadevan]

Lee,

How about trying to plug-in a logging.properties file into the picture and pass in the path of it via the JVM argument -Djava.util.logging.config.file [ I don't know how you are going to be doing it via node though ] and set the log levels to TRACE perhaps and see if that helps ?

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

My Technical Scribbings @ http://rationaleemotions.wordpress.com/

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/8c97332a-5999-4ba0-b720-b3fefd8bfc62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.