Selenium Remote Control 0.9 not works in FireFox 3.0 browser - why?

[Balaji]

Hi All,

Today i start download the latest version of FireFox 3.0 and start execute my Selenium Script, it throws following erro message

16:41:25.186 INFO - Command request: getNewBrowserSession[*chrome, http://192.16\\ 8.2.220:8081/support/Login.jsf] on session null\\ 16:41:26.623 INFO - Launching session 85186\\ 16:41:26.623 WARN - It looks like your baseUrl (http://192.168.2.220:8081/suppor\\ t/Login.jsf) is pointing to a file, not a directory (it doesn't end with a /).\\ We're going to have to strip off the last part of the pathname.\\ 16:41:26.983 INFO - Preparing Firefox profile...\\ 16:41:55.170 WARN - POST /selenium-server/driver/ HTTP/1.1\\ java.lang.RuntimeException: Firefox refused shutdown while preparing a profile\\ at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai\\ tForFullProfileToBeCreated(FirefoxChromeLauncher.java:283)\\ at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau\\ nch(FirefoxChromeLauncher.java:136)\\ at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.lau\\ nchRemoteSession(FirefoxChromeLauncher.java:322)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowse\\ rSession(SeleniumDriverResourceHandler.java:587)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se\\ leniumDriverResourceHandler.java:396)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman\\ dRequest(SeleniumDriverResourceHandler.java:375)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen\\ iumDriverResourceHandler.java:123)\\ 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)\\ Caused by: org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher$Fil\\ eLockRemainedException: Lock file still present! C:\DOCUME~1\sl003093\LOCALS~1\T\\ emp\customProfileDir85186\parent.lock\\ at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai\\ tForFileLockToGoAway(FirefoxChromeLauncher.java:240)\\ at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.wai\\ tForFullProfileToBeCreated(FirefoxChromeLauncher.java:281)\\ ... 15 more\\ 16:41:55.217 INFO - Command request: open[http://192.168.2.220:8081/support/Logi\\ n.jsf, ] on session null\\ 16:41:55.217 WARN - POST /selenium-server/driver/ HTTP/1.1\\ java.lang.NullPointerException\\ at java.util.concurrent.ConcurrentHashMap.get(Unknown Source)\\ at org.openqa.selenium.server.FrameGroupCommandQueueSet.getQueueSet(Fram\\ eGroupCommandQueueSet.java:157)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(Se\\ leniumDriverResourceHandler.java:476)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleComman\\ dRequest(SeleniumDriverResourceHandler.java:375)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(Selen\\ iumDriverResourceHandler.java:123)\\ 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)\\
Please let me know anyone in the group face this issue, how to resolve it?