title: "Chrome Not Reachable" when invoking Selenium scripts from Eclipse IDE
body: <p>In our Selenium remote webdriver set up, we wrote our Selenium Java test scripts for to run in Chrome Browser. We are using Chrome Driver 2.28. Selenium Standalone Server 2.53. Selenium API 2.53. When we run our scripts from with in Eclipse IDE, 3 out of 5 times, the Chrome browser does not get invoked or take a long time to start by the script. When it fails to invoke the browser, it fails with this exception ....</p>
  
  <pre><code>&gt; Caused by: org.openqa.selenium.WebDriverException: chrome not
  &gt; reachable   (Driver info: chromedriver=2.28.455520
  &gt; (cc17746adff54984afff480136733114c6b3704b),platform=Windows NT
  &gt; 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 62.50 seconds
  &gt; Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15
  &gt; 17:00:58' System info: host: '&lt;XXXXXXX&gt;', ip: '&lt;XXXXXXXXXX&gt;',
  &gt; os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
  &gt; java.version: '1.8.0_121' Driver info:
  &gt; org.openqa.selenium.chrome.ChromeDriver
  &gt;         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  &gt;         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
  &gt;         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
  &gt;         at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
  &gt;         at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
  &gt;         at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
  &gt;         at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)
  &gt;         at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:249)
  &gt;         at org.openqa.selenium.remote.RemoteWebDriver.&lt;init&gt;(RemoteWebDriver.java:131)
  &gt;         at org.openqa.selenium.remote.RemoteWebDriver.&lt;init&gt;(RemoteWebDriver.java:144)
  &gt;         at org.openqa.selenium.chrome.ChromeDriver.&lt;init&gt;(ChromeDriver.java:170)
  &gt;         at org.openqa.selenium.chrome.ChromeDriver.&lt;init&gt;(ChromeDriver.java:138)
  &gt;         ... 13 more 11:58:11.356 WARN - Exception: chrome not reachable
  </code></pre>
  
  <blockquote>
    <p>(Driver info: chromedriver=2.28.455520
    (cc17746adff54984afff480136733114c6b3704b),platform=Windows NT
    6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 62.50 seconds
    Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15
    17:00:58' System info: host: '', ip: '',
    os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
    java.version: '1.8.0_121' Driver info:
    org.openqa.selenium.chrome.ChromeDriver
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
            at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)
            at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)
            at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)
            at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:249)
            at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:131)
            at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:144)
            at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:170)
            at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:138)
            ... 13 more 11:58:11.356 WARN - Exception: chrome not reachable</p>
  </blockquote>
  
  <p>The temporary but painful solution is to go to Windows TaskManager and kill the half a dozen or so, Chrome.exe processes one after another. It is observed that even when we run our script or manually running the application, the Chrome browser processes that get invoked are more like 6 or 7, not less.</p>
  
  <p>Is it a Chrome Browser or Selenium issue. ?
  Individually, I used NOT to have this problem unlike my team member who is having this problem since a year. As soon as I upgraded Chrome Driver to 2.28 from 2.25, I started having this problem.</p>