How to fix org.openqa.selenium.remote.http.WebSocket$Listener onError with Selenium WebDriver | BDD

[@boundlessgyan]

Excellent showcasing of the root cause. thanks.

[@testing24x7]

It was really tricky.Thanks for sharing.

[@sdetadda]

Yes it was

[@kishorpawar1314]

Awesome it helped me. Thanks

[@ammu15259]

Its working for me.Thank u so much😍

[@sdetadda]

Glad to hear that

[@satishraja4u]

Worked for me . Thank You :)

[@SingaravelanNatrayan]

thanks for your video , helped me a lot today

[@yoganandbheema6851]

Thankyou its working for me.

[@sdetadda]

You're welcome!

[@SayantaniMajee]

Thanks it worked

[@sdetadda]

Glad it helped

[@vineetbhargav9834]

hi Ragvendra, I face same issue, when use quit() it not showing any error on console but when use close() it show org.openqa.selenium.remote.http.WebSocket$Listener onError. is there any solution for when we use only close () methods. pls share it

[@suryapbhoi]

Thank you

[@sdetadda]

You're welcome

[@gandhigeerthana2058]

In PageObject model. I’m getting null pointer @Test part but it running @Beforetest well😢

[@bireswarghosal1525]

But the purpose of using close() and quit() is totally different if I need to use close() then on that case what will be the solution ?

[@harishkce1989]

WIll it not be a problem if tests are executed in parallel ? driver.quit(); will close all instances of the browser especially ?

[@sdetadda]

Adding remote-allow-origins argument to the ChromeDriver constructor may help you fix/resolve the warning.
ChromeOptions options = new ChromeOptions();
options.addArguments("--remote-allow-origins=*");
WebDriver driver = new ChromeDriver(options);

[@harishkce1989]

@@sdetadda options.addArguments("--remote-allow-origins=*") i added this option too...still resulting in same warning message unfortunately

[@sdetadda]

1.Try adding latest selenium server jar/dependencies
2.be sure to quit/close/flush all driver instances before starting the script execution.
Let me know if it works, share with me your test script/class file otherwise?

[@sdetadda]

Also ensure the driver and actual browser version matches/ are compatible.

[@harishkce1989]

Is it consider error or warning ?? cos in my case test case did not fail..

[@sdetadda]

Its WARNING and seems harmless as long as test execution is concerned.

[@Pedrotester]

In my case it doesnt work changing to quit(), the error is showing again

[@sdetadda]

Try to pick the latest selenium dependencies from mvnrepository or add remote-allow-origins while initializing the driver,
ChromeOptions options = new ChromeOptions();
options.addArguments("--remote-allow-origins=*");
WebDriver driver = new ChromeDriver(options);

[@cgraham74]

I am using Chrome driver options as well as I use driver.quit(). I still get intermittent Socket Exceptions@@sdetadda

[@nikitatuteja8320]

doesnt work

[@nikitatuteja8320]

In my case it doesnt work changing to quit(), the error is showing again