-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Communicating with Remote Browser #1810
Comments
`ERROR [3409] org.openqa.selenium.remote.server.handler.FindElement - Unexpected exception during findElement ` |
You need to upgrade to the latest selenium (2.52). Stacktrace shows you are using 2.46 |
@lukeis Thanks for the reply. Hope you can give some more pointers, Thanks.
|
I met this exception too. It always occurs when I call executeScript too
|
@lukeis , @Handsome2734 : We upgraded to 2.53 and pheww the same issue again. |
You'll need to provide some kind of way to reproduce the issue. Also might be nice to have the log from the node when this occurs |
Can not find a way to 100% reproduce this issue. But when I add log4j module
|
Hi @lukeis @Handsome2734 , We are running tests with 30 browser threads in Linux machine. This issue occurs very randomly.There is no exact steps to reproduce. Everytime it fails different test cases. Client side Exception: Selenium node side exception: |
@gurvinderd when this happens can you view the node directly? can you see if there's a Firefox instance still up / hung? (the message indicates it probably crashed though). Do you potentially have a system problem? (Disk space, cpu over utilized, something else?) |
If the browser is still up, getting the browser console log would be helpful (ctrl+shift J) |
@lukeis Thanks for the reply. This error occurs once in thousand test. It is not possible for us to check if browser actually crashed or not. Is there any limitation on max browser a node can handle? Or is there is limitation to hub ?Machine we are using is very powerful and it has enough ram even after 30 browsers. |
Hi @lukeis |
This got resolved. Upgrading the ff fixed this issue. Thanks everyone for helping on this. |
I'm getting a similar issue. The only message I get is this:
The error is being thrown in
When I put a breakpoint there the value of |
getting error when i open the browser before it was working fine! any suggestion pls? FAILED CONFIGURATION: @BeforeMethod open SKIPPED CONFIGURATION: @AfterMethod Logout
Default suite Configuration Failures: 1, Skips: 5[TestNG] Time taken by org.testng.reporters.jq.Main@7921b0a2: 14 ms |
FWIW, pasting a long stack trace is not a replacement for a reproducible test case. |
I can see this issue has been reported earlier but didn't find any concrete solution.
Issue happens randomly on any test and once in 10 execution.
Can someone help, Thanks.
org.openqa.selenium.WebDriverException: Error communicating with the remote browser. It may have died. Build info: version: '2.46.0', revision: '87c69e2', time: '2015-06-04 16:16:47' System info: host: 'hub', ip: '*', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-573.8.1.el6.x86_64', java.version: '1.8.0_45-internal' Driver info: driver.version: EventFiringWebDriver Command duration or timeout: 421 milliseconds Build info: version: '2.46.0', revision: '61506a4624b13675f24581e453592342b7485d71', time: '2015-06-04 10:22:50' System info: host: '*', ip: '*', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-573.8.1.el6.x86_64', java.version: '1.7.0_76' *** Element info: {Using=css selector, value=.btn-action.tif-new} Session ID: de133790-7d12-4d98-83da-5a5bd7191138 Driver info: org.openqa.selenium.remote.RemoteWebDriver Capabilities [{platform=LINUX, javascriptEnabled=true, acceptSslCerts=true, browserName=firefox, rotatable=false, locationContextEnabled=true, webdriver.remote.sessionid=de133790-7d12-4d98-83da-5a5bd7191138, version=42.0, cssSelectorsEnabled=true, databaseEnabled=true, handlesAlerts=true, webStorageEnabled=true, nativeEvents=false, applicationCacheEnabled=true, takesScreenshot=true}] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204) at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:605) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:358) at org.openqa.selenium.remote.RemoteWebDriver.findElementByCssSelector(RemoteWebDriver.java:447) at org.openqa.selenium.By$ByCssSelector.findElement(By.java:426) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:350) at org.openqa.selenium.support.pagefactory.DefaultElementLocator.findElement(DefaultElementLocator.java:69) at org.openqa.selenium.support.pagefactory.internal.LocatingElementHandler.invoke(LocatingElementHandler.java:38) at com.sun.proxy.$Proxy17.click(Unknown Source) at com.*.BaseElement.click(BaseElement.java:71) at com.*.WaitEnabledBaseElement.click(WaitEnabledBaseElement.java:34) ***** at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.openqa.selenium.remote.UnreachableBrowserException: Error communicating with the remote browser. It may have died. Build info: version: '2.46.0', revision: '87c69e2', time: '2015-06-04 16:16:47' System info: host: 'hub', ip: '*', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-573.8.1.el6.x86_64', java.version: '1.8.0_45-internal' Driver info: driver.version: EventFiringWebDriver Build info: version: '2.46.0', revision: '61506a4624b13675f24581e453592342b7485d71', time: '2015-06-04 10:22:50' System info: host: '*', ip: '*', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-573.8.1.el6.x86_64', java.version: '1.7.0_76' Driver info: driver.version: unknown
The text was updated successfully, but these errors were encountered: