in our selenium remote webdriver set up, wrote our selenium java test scripts run in chrome browser. using chrome driver 2.28. selenium standalone server 2.53. selenium api 2.53. when run our scripts in eclipse ide, 3 out of 5 times, chrome browser not invoked or take long time start script. when fails invoke browser, fails exception ....
> caused by: org.openqa.selenium.webdriverexception: chrome not > reachable (driver info: chromedriver=2.28.455520 > (cc17746adff54984afff480136733114c6b3704b),platform=windows nt > 6.1.7601 sp1 x86_64) (warning: server did not provide 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: '<xxxxxxx>', ip: '<xxxxxxxxxx>', > os.name: 'windows 7', os.arch: 'amd64', os.version: '6.1', > java.version: '1.8.0_121' driver info: > org.openqa.selenium.chrome.chromedriver > @ sun.reflect.nativeconstructoraccessorimpl.newinstance0(native method) > @ sun.reflect.nativeconstructoraccessorimpl.newinstance(nativeconstructoraccessorimpl.java:62) > @ sun.reflect.delegatingconstructoraccessorimpl.newinstance(delegatingconstructoraccessorimpl.java:45) > @ java.lang.reflect.constructor.newinstance(constructor.java:423) > @ org.openqa.selenium.remote.errorhandler.createthrowable(errorhandler.java:206) > @ org.openqa.selenium.remote.errorhandler.throwifresponsefailed(errorhandler.java:158) > @ org.openqa.selenium.remote.remotewebdriver.execute(remotewebdriver.java:678) > @ org.openqa.selenium.remote.remotewebdriver.startsession(remotewebdriver.java:249) > @ org.openqa.selenium.remote.remotewebdriver.<init>(remotewebdriver.java:131) > @ org.openqa.selenium.remote.remotewebdriver.<init>(remotewebdriver.java:144) > @ org.openqa.selenium.chrome.chromedriver.<init>(chromedriver.java:170) > @ org.openqa.selenium.chrome.chromedriver.<init>(chromedriver.java:138) > ... 13 more 11:58:11.356 warn - exception: chrome not reachable (driver info: chromedriver=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),platform=windows nt 6.1.7601 sp1 x86_64) (warning: server did not provide 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 @ sun.reflect.nativeconstructoraccessorimpl.newinstance0(native method) @ sun.reflect.nativeconstructoraccessorimpl.newinstance(nativeconstructoraccessorimpl.java:62) @ sun.reflect.delegatingconstructoraccessorimpl.newinstance(delegatingconstructoraccessorimpl.java:45) @ java.lang.reflect.constructor.newinstance(constructor.java:423) @ org.openqa.selenium.remote.errorhandler.createthrowable(errorhandler.java:206) @ org.openqa.selenium.remote.errorhandler.throwifresponsefailed(errorhandler.java:158) @ org.openqa.selenium.remote.remotewebdriver.execute(remotewebdriver.java:678) @ org.openqa.selenium.remote.remotewebdriver.startsession(remotewebdriver.java:249) @ org.openqa.selenium.remote.remotewebdriver.(remotewebdriver.java:131) @ org.openqa.selenium.remote.remotewebdriver.(remotewebdriver.java:144) @ org.openqa.selenium.chrome.chromedriver.(chromedriver.java:170) @ org.openqa.selenium.chrome.chromedriver.(chromedriver.java:138) ... 13 more 11:58:11.356 warn - exception: chrome not reachable
the temporary painful solution go windows taskmanager , kill half dozen or so, chrome.exe processes 1 after another. observed when run our script or manually running application, chrome browser processes invoked more 6 or 7, not less.
is chrome browser or selenium issue. ? individually, used not have problem unlike team member having problem since year. upgraded chrome driver 2.28 2.25, started having problem.
if running script root user, throw error "chrome not reachable". try running script normal user, work fine.
Comments
Post a Comment