Skip to content
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

java.lang.RuntimeException: unable to call device farm endpoints java.io.IOException: HTTP/1.1 header parser received no bytes #1218

Open
kutobot opened this issue Apr 14, 2024 · 7 comments

Comments

@kutobot
Copy link

kutobot commented Apr 14, 2024

while trying to run ATD in distribute or parallel mode, facing below exception. Any ideas? how to fix this please

java.lang.RuntimeException: unable to call device farm endpoints java.io.IOException: HTTP/1.1 header parser received no bytes

at com.appium.utils.Api.getResponse(Api.java:29)
at com.appium.device.Devices.getConnectedDevices(Devices.java:26)
at com.appium.manager.ATDRunner.<init>(ATDRunner.java:40)
at com.appium.tests.Runner.testRunner(Runner.java:13)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:135)
at org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:673)
at org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:220)
at org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:50)
at org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:945)
at org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:193)
at org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.testng.TestRunner.privateRun(TestRunner.java:808)
at org.testng.TestRunner.run(TestRunner.java:603)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:429)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:423)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:383)
at org.testng.SuiteRunner.run(SuiteRunner.java:326)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1249)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
at org.testng.TestNG.runSuites(TestNG.java:1092)
at org.testng.TestNG.run(TestNG.java:1060)
at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:65)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:105)
@kutobot
Copy link
Author

kutobot commented Apr 14, 2024

facing it on
[Appium] Appium REST http interface listener started on http://xxxxx/wd/hub
[Appium] Available drivers:
[Appium] - [email protected] (automationName 'UiAutomator2')
[Appium] - [email protected] (automationName 'XCUITest')
[Appium] Available plugins:
[Appium] - [email protected]
[Appium] - [email protected] (ACTIVE)
[Appium] - [email protected]

@saikrishna321
Copy link
Member

@kutobot Please try with latest ATD. This issue was fixed

@kutobot
Copy link
Author

kutobot commented Apr 14, 2024

hey @saikrishna321 upgraded pom.xml to 14.0.4, above issue is fixed. But i am ending up with
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

@kutobot
Copy link
Author

kutobot commented Apr 14, 2024

[Appium] Available drivers:
[Appium] - [email protected] (automationName 'UiAutomator2')
[Appium] - [email protected] (automationName 'XCUITest')
[Appium] Available plugins:
[Appium] - [email protected]
[Appium] - [email protected]
[Appium] - [email protected] (ACTIVE)

i have the above drivers and plugins

@kutobot
Copy link
Author

kutobot commented Apr 14, 2024

now i am ending up with below, after adding surefire plugin to fix the above issue :)

[HTTP] <-- GET /wd/hub/status 200 7 ms - 199
[HTTP]
1
[HTTP] --> GET /device-farm/api/device
[HTTP] {}
[device-farm-main] Received non-webdriver request with url /device-farm/api/device. So, not proxying it to downstream.
[HTTP] --> GET /dashboard/api/ping
[HTTP] {}
[device-farm-main] Received non-webdriver request with url /dashboard/api/ping. So, not proxying it to downstream.
[HTTP] No route found for /dashboard/api/ping
[HTTP] <-- GET /dashboard/api/ping 404 3 ms - 211
[HTTP]
[HTTP] <-- GET /device-farm/api/device 200 37 ms - 412
[HTTP]
...
... TestNG 7.7.0 by Cédric Beust ([email protected])
...

[HTTP] --> GET /device-farm/api/cliArgs
[HTTP] {}
[device-farm-main] Received non-webdriver request with url /device-farm/api/cliArgs. So, not proxying it to downstream.
[HTTP] <-- GET /device-farm/api/cliArgs 200 1 ms - 999
[HTTP]
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

@saikrishna321
Copy link
Member

Share full logs in gist

@kutobot
Copy link
Author

kutobot commented Apr 14, 2024

SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

https://gist.github.com/kutobot/198df1443c23739576cfa147f047b64b @saikrishna321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants