com.thoughtworks.selenium.SeleniumException

Connection refused: connect at com.thoughtworks.selenium.HttpCommandProcessor.executeCommandOnServlet(HttpCommandProcessor.java: 111) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java: 90) at com.thoughtworks.selenium.DefaultSelenium.captureScreenshot(DefaultSelenium.java: 719) at com.thoughtworks.selenium.ScreenshotListener.onTestFailure(ScreenshotListener.java: 27) at com.thoughtworks.selenium.ScreenshotListener.onConfigurationFailure(ScreenshotListener.java: 41) at org.testng.internal.Invoker.runConfigurationListeners(Invoker.java: 1791) at org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java: 323)

Samebug tips4

Check if your MongoDB is available.

Check if your server (or a proxy server) is not going up and down. There might be something between a proxy and a client sending intermittent requests to non-functioning hosts as well. There might as well be too many requests in a short amount of time.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web141

  • via Google Groups by John, 11 months ago
    Connection refused: connect at com.thoughtworks.selenium.HttpCommandProcessor.executeCommandOnServlet(HttpCommandProcessor.java: 111) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java: 90
  • Connection refused: > > connect at > > > com.thoughtworks.selenium.HttpCommandProcessor.executeCommandOnServlet(HttpCommandProcessor.java: > > 121) at > > > com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java: > > 101
  • via Google Groups by rechu, 1 year ago
    Timed out after 30000ms at > com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError > (HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand > (HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.open > (DefaultSelenium.java:335)
  • Stack trace

    • com.thoughtworks.selenium.SeleniumException: Connection refused: connect at com.thoughtworks.selenium.HttpCommandProcessor.executeCommandOnServlet(HttpCommandProcessor.java: 111) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java: 90) at com.thoughtworks.selenium.DefaultSelenium.captureScreenshot(DefaultSelenium.java: 719) at com.thoughtworks.selenium.ScreenshotListener.onTestFailure(ScreenshotListener.java: 27) at com.thoughtworks.selenium.ScreenshotListener.onConfigurationFailure(ScreenshotListener.java: 41) at org.testng.internal.Invoker.runConfigurationListeners(Invoker.java: 1791) at org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java: 323) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:226) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.TestRunner.beforeRun(TestRunner.java:632) at org.testng.TestRunner.run(TestRunner.java:600) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:203) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.<init>(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    18 times, 8 hours ago
    123 times, 11 hours ago
    47 times, 1 day ago
    279 more bugmates