-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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]: Client times out creating a session after running a number of successful sessions #13718
Comments
@Vlatombe, 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! |
Do you see the issue if you use Chrome or Edge? Just trying to locate where the problem might be. |
I'll check with Chrome just in case, however given the reverse proxy workaround, I'm doubting this has anything to do with the browser used. |
FWIW I ran the same suite on chrome, exact same result |
I had a look at the code and did find an field read with missing synchronize statement, will fix this the next days. But i don't think this is the root cause here. Increasing the client timeout might produce another error message (6 minutes should be fine) and might help to find the root cause. Some of the default grid timeouts are higher than the default client timeout, this is allready tracked in other issues. |
What happened?
We run the Jenkins Acceptance Test harness. We recently migrated from Selenium 4.11.0 to 4.18.1 (jenkinsci/acceptance-test-harness#1499) but got stuck because of execution issues that were not occurring before.
Our environment runs subsets of the tests suite inside a docker environment:
selenium/standalone-firefox:4.18.1
All tests run sequentially, so it is expected that only one selenium session is active at a given time.
Obviously both client and server are aligned.
We managed to narrow down the issue to the
4.13.0
->4.14.1
selenium upgrade.The symptoms are the following:
HTTP 200
onPOST /session
)All the tests are launched using the initialization sequence (link), so the problem is clearly not tied to one test content.
I managed to find a workaround for this problem: I added a proxy server (
caddy reverse-proxy --from :4444 --to firefox:4444 --insecure
) between the client and selenium server and the problem went away.How can we reproduce the issue?
I never managed to reproduce the problem locally on a Mac, running the same tests against a local selenium server.
Even though I never tracked down the root cause for this, it is probably network stack related. The fact it started to appear just after migrating to
4.14
, matching with the JDK http client switch, makes me think it could be related to the problem, even though it seems to affect the server side (a new JVM is forked for each new test class).I'm hoping this eventually helps to diagnose a possible issue, and leave it for posterity in case anyone faces a similar problem.
Relevant log output
Client side exception
Server-side logging
The text was updated successfully, but these errors were encountered: