Firefox profile timeout in selenium-server only from ANT?

[Gil Novak]

If I start selenium-server by hand and run my test, it works fine. But when I use the ant targets from this page:
http://wiki.openqa.org/display/SRC/Selenium-RC+and+Continuous+Integration
The test can't run because the selenium server times out creating the firefox profile.

I'm on Centos 5. I may have had a successful run once last week, while playing with the -timeout argument, but that was a fluke, because, I noticed on this page:
http://svn.openqa.org/fisheye/browse/selenium-rc/trunk/server-coreless/src/main/java/org/openqa/selenium/server/browserlaunchers/FirefoxCustomProfileLauncher.java?r=1914
on line 129, that the timeout is hardcoded to 20 seconds. So, my one possible successful run may have possibly beaten that timeout.

Here's the error in the selenium-server log:

14:03:24.515 INFO [11] org.openqa.selenium.server.SeleniumDriverResourceHandler - Command request: getNewBrowserSession[*firefox, http://vmnode-006:17000] on session null\\ 14:03:24.577 INFO [11] org.openqa.selenium.server.SeleniumDriverResourceHandler - Launching session 804515\\ 14:03:24.581 DEBUG [11] org.openqa.selenium.server.browserlaunchers.FirefoxCustomProfileLauncher - customProfileDir = /tmp/customProfileDir804515\\ 14:03:24.583 DEBUG [11] org.openqa.selenium.server.browserlaunchers.ResourceExtractor - Extracting /customProfileDirCUSTFF to /tmp/customProfileDir804515\\ 14:03:24.594 INFO [11] org.openqa.selenium.server.browserlaunchers.FirefoxCustomProfileLauncher - Preparing Firefox profile...\\ 14:03:44.721 WARN [11] org.mortbay.http.HttpConnection - POST /selenium-server/driver/ HTTP/1.1\\ java.lang.RuntimeException: Timed out waiting for profile to be created!\\ at org.openqa.selenium.server.browserlaunchers.FirefoxCustomProfileLauncher.waitForFullProfileToBeCreated(FirefoxCustomProfileLauncher.java:271)\\ at org.openqa.selenium.server.browserlaunchers.FirefoxCustomProfileLauncher.launch(FirefoxCustomProfileLauncher.java:147)\\ at org.openqa.selenium.server.browserlaunchers.AbstractBrowserLauncher.launchRemoteSession(AbstractBrowserLauncher.java:24)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowserSession(SeleniumDriverResourceHandler.java:587)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(SeleniumDriverResourceHandler.java:396)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handleCommandRequest(SeleniumDriverResourceHandler.java:375)\\ at org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.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)\\ 14:03:44.727 DEBUG [11] org.mortbay.http.HttpConnection - RESPONSE:\\ HTTP/1.1 500 Internal Server Error\\ Date: Mon, 02 Jun 2008 18:03:24 GMT\\ Server: Jetty/5.1.x (Linux/2.6.18-53.1.14.el5 amd64 java/1.6.0_05\\ Connection: close\\