-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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]: unhandled exception in grid is reported as ScriptTimeoutException
on the client
#12484
Comments
@joerg1985, 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! |
@diemol could you have a look at the suggested fix for this? |
@joerg1985 I believe you are correct. Feel free to push the fix, thank you! |
has been fixed in c62fe6c, with some other small issues. |
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?
We had a connection issue between the standalone server and the driver, this did raise a strange exception on the client side.
org.openqa.selenium.ScriptTimeoutException: Unable to execute request for an existing session: java.net.ConnectException: Connection refused: no further information: localhost/[0:0:0:0:0:0:0:1]:42081
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10 x64
Selenium version
Java 4.9.1
What are the browser(s) and version(s) where you see this issue?
all
What are the browser driver(s) and version(s) where you see this issue?
all
Are you using Selenium Grid?
standalone 4.9.1
The text was updated successfully, but these errors were encountered: