-
-
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]: remote selenium fails to respond to start new connections after some criteria #12421
Comments
@jtnord, 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! |
Can you share the container logs? |
this was some normal runs, followed by an interactive run, followed by an interactive run that hung (and then failed to start a new session) |
The last two log entries show that the session was created, and it looks like no more commands were received. Have you checked on the client side what happens when the session hangs? |
I think that was the previous session not the one that hung because the session could not be created - I will do a clear separation with just 2 runs.
yes - but given the server was "blocked" in For completeness the client stack is below - which shows it is hanging wating for the session to be created.
|
Please move to the Java 11 HTTP client, try again, and if there is anything failing, we can check again. |
I will close this, and if the issue is still present, we can reopen it. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
Discovered in the Jenkins ATH suite (in the case of a potentially non clean shutdown?), subsequent sessions can not be started and timeout. After a while (many minutes) this fixes it self,
this seemed to be introduced in the 4.x (3.x seemed to work ok)
How can we reproduce the issue?
Relevant log output
the selenium server in the container appears to be waiting for something that has not happened.
(below stack was from 4.10 but same issue happens with the latest release)
full stack trace :
Operating System
Windows 11
Selenium version
4.10
What are the browser(s) and version(s) where you see this issue?
firefox, chrome
What are the browser driver(s) and version(s) where you see this issue?
whatever is in the container
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: