URI has an authority component error

[Marc Holden]

Has anybody ever run into this error? I am running the latest selenium-rc binaries (0.9.0). Everything works fine if I run from eclipse but when trying to run Rational Test Manager I get this error. I am using Windows XP as my test platform. All the jar files on my classpath are accessed with UNC names (i.e. \\ machine\libdir\jarfile.jar)


INFO Selenium Server Thread HttpServer.java(684) - Version Jetty/0.9.0
INFO Selenium Server Thread Container.java(74) - Started HttpContext[/,/]
INFO Selenium Server Thread Container.java(74) - Started HttpContext[/selenium-server,/selenium-server]
INFO Selenium Server Thread Container.java(74) - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
INFO Selenium Server Thread SocketListener.java(204) - Started SocketListener on 0.0.0.0:4444
INFO Selenium Server Thread Container.java(74) - Started org.mortbay.jetty.Server@1df280b
INFO Thread-0 TestLaunchSelenium.java(262) - Test [1] description: null
INFO SocketListener0-1 FileResource.java(60) - Checking Resource aliases
WARN SocketListener0-1 HttpConnection.java(780) - GET /selenium-server/driver/?cmd=getNewBrowserSession&1=*chrome&2=http%3A%2F%2F192.168.18.136%3A8080%2Fcwest_web HTTP/1.1
*java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.{code:html}<init>{code}(Unknown Source)
at org.openqa.selenium.server.browserlaunchers.ResourceExtractor.getJarFileFromUrl(ResourceExtractor.java:93)
at org.openqa.selenium.server.browserlaunchers.ResourceExtractor.extractResourcePath(ResourceExtractor.java:36)
at *org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.makeCustomProfile(FirefoxChromeLauncher.java:151)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launch(FirefoxChromeLauncher.java:113)
at org.openqa.selenium.server.browserlaunchers.AbstractBrowserLauncher.launchRemoteSession(AbstractBrowserLauncher.java:24)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowserSession(SeleniumDriverResourceHandler.java:470)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(SeleniumDriverResourceHandler.java:316)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleCommandRequest(SeleniumDriverResourceHandler.java:296)
at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:129)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

[Matt Hesseling]

In the line:
/selenium-server/driver/?cmd=getNewBrowserSession&1=*chrome&2=http%3A%2 F%2F192.168.18.136%3A8080%2Fcwest_web HTTP/1.1

There is a space in http:%3A%2 F%2F192.168.18.136 between the first '2' and 'F' characters that should not be there. I'm not exactly sure why the space is there, but I'm pretty sure that that is what's causing the exception.

[Marc Holden]

I have done two things that seem to have resolved the problem. I am not sure which actually fixed it (and to lazy to track it down) but I did:

1. Build Selenium-Server and java client from latest source code.
2. Updated class path to not use UNC naming for selenium jar files.

Based on the location of the error I think that it was step 2 that actually fixed the problem.