Issue 3450 in selenium: Grid 2.0.19 fails on remote execution when launching browser

[sele...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3450 by mguer...@gmail.com: Grid 2.0.19 fails on remote execution
when launching browser
http://code.google.com/p/selenium/issues/detail?id=3450

What steps will reproduce the problem?
1. In server computer (ip 192.168.1.211) Open grid hub with attached
run-hub.bat and hub.json file.
2. In node computer (ip 192.168.1.212) Open the node rc with attached
run-rcnode-standard.htm. At this point check Ok that both the hub and
node can communicate each other. The node is reflected in hub console.
3. Run using eclipse the scripts using rc in localhost:4444

What is the expected output? What do you see instead?
The espected is to have selenium opening browser and running scripts.
However in eclipse I see the error message "java.lang.AssertionError:
SuiteGenera ERROR: Open Selenium Session->Cannot start Selenium RC session.
Could not start Selenium session:
org%2Eopenqa%2Egrid%2Ecommon%2Eexception%2EGridException%3A+Error+forwarding+the+new+session+The+server+returned+an+error+%3A+Failed+to+start+new+browser+session%3A+Error+while+launching+browser

When moved the node to DEBUG mode I can get a detailed trace as:

06:44:04.501 INFO - Command request: getNewBrowserSession[*firefox,
http://www.genera.cl/, ] on session null
06:44:04.501 INFO - creating new remote session
06:44:04.501 DEBUG - Requested browser string '*firefox' matches *firefox
06:44:04.501 INFO - Allocated session d1ee273cff8e4b67be5f20995f3b3a79 for
http://www.genera.cl/, launching...
06:44:04.516 ERROR - Failed to start new browser session, shutdown browser
and clear all session data
java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.<init>(Unknown Source)
at
org.openqa.selenium.server.browserlaunchers.ResourceExtractor.getJarFileFromUrl(ResourceExtractor.java:103)
at
org.openqa.selenium.server.browserlaunchers.ResourceExtractor.extractResourcePath(ResourceExtractor.java:39)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.extractProfileFromJar(FirefoxChromeLauncher.java:181)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.makeCustomProfile(FirefoxChromeLauncher.java:223)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launch(FirefoxChromeLauncher.java:89)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launchRemoteSession(FirefoxChromeLauncher.java:412)
at
org.openqa.selenium.server.browserlaunchers.FirefoxLauncher.launchRemoteSession(FirefoxLauncher.java:114)
at
org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSession(BrowserSessionFactory.java:374)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession(BrowserSessionFactory.java:125)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession(BrowserSessionFactory.java:86)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowserSession(SeleniumDriverResourceHandler.java:811)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(SeleniumDriverResourceHandler.java:437)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handleCommandRequest(SeleniumDriverResourceHandler.java:407)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:151)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
at
org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
at
org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
at
org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
at
org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
at
org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
at
org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
06:44:04.532 DEBUG - clearing queue set
06:44:04.610 INFO - Got result: Failed to start new browser session: Error
while launching browser on session null
06:44:04.610 DEBUG - Handled by
org.openqa.selenium.server.SeleniumDriverResourceHandler in
HttpContext[/selenium-server,/selenium-server]
06:44:04.610 DEBUG - RESPONSE:
HTTP/1.1 200 OK

Selenium version: 2.0.19
OS: Windows 7 64 bits (virtualized computers)
Browser: any
Browser version: any

I think this is the most trivial use case, and used standard .json config
files, so I didn't expect it to fail. I tested the hub and node config
locally and worked Ok with same tests so it's not a config problem.
The communications both sides looks OK, but the failure is thrown
internally when attempt to launch the broswer after get the session. My
guess is a failure on code.

Attachments:
hub.json 324 bytes
run-hub.bat 333 bytes
node-rc-standard.json 670 bytes
run-rcnode-standard.bat 613 bytes

[sele...@googlecode.com]

Updates:
Labels: Component-Grid

Comment #1 on issue 3450 by barancev: Grid 2.0.19 fails on remote execution

when launching browser
http://code.google.com/p/selenium/issues/detail?id=3450

(No comment was entered for this change.)

[sele...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 3450 by barancev: Grid 2.0.19 fails on remote execution

when launching browser
http://code.google.com/p/selenium/issues/detail?id=3450

Fixed by r16972, should be included in 2.22