Selenium Webdriver error - HTTP remote request time out

[alexlosk]

Hi all,

I've created a simple test case to open a chorme browser remotelly.
I've also set up my virtual machine with the expected information and it works so far:

one.png (8.35 KiB) Viewed 1073 times

I've also installed the standalone server and the chromedriver and I just executed in the CMD:

java -jar -Dwebdriver.chrome.driver=chromedriver.exe selenium-server-standalone-3.12.0.jar

The response was a bit strange:

16:38:01.410 INFO [GridLauncherV3.launch] - Selenium build info: version: '3.12.0', revision: '7c6e0b3'
16:38:01.412 INFO [GridLauncherV3$1.launch] - Launching a standalone Selenium Server on port 4444
2018-06-25 16:38:01.540:INFO::main: Logging initialized @528ms to org.seleniumhq.jetty9.util.log.StdErrLog
16:38:01.970 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
2018-06-25 16:38:04.085:WARN:osjh.HttpParser:qtp26117480-14: Illegal character 0x16 in state=START for buffer [email protected][p=1,l=164,c=8192,r=163]={\x16<<<\x03\x03\x00\x9f\x01\x00\x00\x9b\x03\x03[0\xFeKEd\x8d...\x06\x03\x00#\x00\x00\x00\x17\x00\x00\xFf\x01\x00\x01\x00>>>\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
2018-06-25 16:38:04.231:WARN:osjh.HttpParser:qtp26117480-11: Illegal character 0x16 in state=START for buffer [email protected][p=1,l=164,c=8192,r=163]={\x16<<<\x03\x03\x00\x9f\x01\x00\x00\x9b\x03\x03[0\xFeL\x04\x13d...\x06\x03\x00#\x00\x00\x00\x17\x00\x00\xFf\x01\x00\x01\x00>>>\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}

Are these statements errors normal?

My problem comes when I run the test from my local machine, there is an error and the test does not work:

two.png (61.03 KiB) Viewed 1072 times

Thanks in advance.
BR

[McTurtle]

Hello Alex,

What happens if you remove your endpoint configuration?
Can you share your endpoint configuration? I am suspecting that the issue will not appear if you remove the configuration and that I might be able to replicate it by using the same configuration

Regards,
McTurtle

[Fovink]

Hi,

Was there a solution for this problem? I am having the same issues, but with IE11. Chrome and Edge are both running fine with Selenium. When I remove the endpoint and just use IE, I am also not having any problems.

[McTurtle]

Hi Fovink,

Are you using the newest version of Selenium and the IE webdriver?
Do you have an endpoint configuration? What happens if you remove it and start without it?

Regards,
McTurtle

[Fovink]

Hi McTurtle,

Thanks for your response.
Yes, I have the newest versions of Selenium and IE webdriver. And yes, I have an endpoint configuration. When I remove the configurations the tests still fail. I don't see a time out in the Ranorex report, but this message: Unable to determine type from: E. Last 1 characters read: E

Regards,
Fovink

[McTurtle]

Hi Fovink,

OK... I suspect that you are doing something non-standard in the start browser action or so ("E", "IE", you get it ). Please create a new solution and only add the actions needed to replicate the issue. After that, post a compressed Ranorex Solution with your next reply. You can create the compressed Ranorex Solution like this: Creating a compressed Ranorex solution

Can't wait to dig into it

Regards,
McTurtle

[Fovink]

Hi,

I made a new solution and tried again with the webdriver. I get both the E thing message and time outs. It seems that it does not matter if I have a configuration or not for my end point. The only way to get IE to work is to remove the Selenium endpoint all together and just use my local machine as an endpoint.

However, you said something about the start browser action, in all cases the browser is correctly started and it navigates to the correct URL. The message is shown later.

Kind regards,
Fovink

[McTurtle]

Hi Fovink,

In the last run you seem to not have encountered the timeout. If there would be the timeout, then the test would not run long enough to see this error message. So, you sometimes see the timeout and sometimes this error?

Please post the full stacktace of the error in the screenshot of the last email. Also, please create a compressed Ranorex solution as already requested in my previous post and attach it to your next reply.

Regards,
McTurtle