-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[🐛 Bug]: Unexpected HTTP response status code 400 error when running tests inside chrome-standalone docker container #14842
Comments
@jonn-set, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
#14410 did limit the number of websocket connections per session, i think you hit this limit. |
@jonn-set are you calling |
Yes, I am, will try doing it only once when I set it up and check. Will try increasing the nodes setting if the first option doesn't work. Thanks @joerg1985, appreciate your help. Will get back whatever the result is. Thank you. |
@joerg1985 augmenting only once seem to have worked. Thanks for your help, appreciate your keen eye to details. Out of interest, how do you override the max websocket connections per session? Where we do do that config? |
The This should be better documented on the webpage, i did not expect the PR to get merged this fast. @pujagani do you think it does make sense to add a warning to the log, when one driver instance is augmented multiple times? Or silently returing the previously created agumented driver should be possible too. |
Thanks @joerg1985 is the configuration something we can set when starting the selenium-standalone Docker Container, if yes, is it this variable |
|
@joerg1985 I think its a good idea to add a warning to the log when augmented more than once. |
What happened?
I recently upgraded to 4.26 from 4.23 and have been facing intermittent issue running tests inside a Selenium Standalone chrome docker container v 130
The point where this is happening is when I call
new Augmenter().augment(driver)
. However the same code works fine for a lot of tests before it starts failing. The exact error isjdk.internal.net.http.websocket.CheckFailedException: Unexpected HTTP response status code 400
.I am trying to intercept a HTTP Request (Response as well sometimes), but before I do that I have to augment the driver instance as its a
RemoteWebDriver
instance and that's when the exception is being thrown. I have not seen this happen when I am running it locally on a Windows 10 machine.How can we reproduce the issue?
Relevant log output
Operating System
RHEL8
Selenium version
Java 4.26
What are the browser(s) and version(s) where you see this issue?
Chrome 130
What are the browser driver(s) and version(s) where you see this issue?
chromedriver 130
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: