java.net.SocketException: Connection reset on Selenium driver.close() or driver.quit() statements

Question

I am seeing a java.net.SocketException: Connection reset almost every time I use a driver.close() or driver.quit() statement. The browser does get closed and the exception isn't affecting any of my tests so far, but I would still like to understand why this is happening.

I checked for a version incompatibility, but the issue persists even after I updated my ChromeDriver. (I'm using ChromeDriver 84.0.4147.30 with Google Chrome Version 84.0.4147.105.)

The issue is intermittent, but usually occurs about 80% of the time.

Code:

public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver","/chromedriver.exe");
        WebDriver driver = new ChromeDriver();
        driver.get("https://www.google.com/");
        driver.close();
        System.exit(0);
    }

Error:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Starting ChromeDriver 84.0.4147.30 (48b3e868b4cc0aa7e8149519690b6f6949e110a8-refs/branch-heads/4147@{#310}) on port 24445
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
Aug 07, 2020 6:39:11 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: W3C
Aug 07, 2020 6:39:14 PM org.openqa.selenium.remote.http.WebSocket$Listener onError
WARNING: Connection reset
java.net.SocketException: Connection reset
    at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:345)
    at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:376)
    at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
    at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
    at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.base/java.lang.Thread.run(Thread.java:832)


Process finished with exit code 0

Getting the same error here with latest chromedriver and chrome (114.0.5735.90) and Selenium 4.10.0 — Lenny Primak
– Lenny Primak, Commented Jul 12, 2023 at 1:34
See answer stackoverflow.com/questions/72540689/… which worked for me — Lenny Primak
– Lenny Primak, Commented Jul 12, 2023 at 1:42

Shubham Rathi · Accepted Answer · 2023-10-09 05:01:58Z

1

Are you using driver listeners? If yes, then driver is getting called even after quit and hence the error.

answered Oct 9, 2023 at 5:01

Shubham Rathi

11 bronze badge

Sign up to request clarification or add additional context in comments.

1 Comment

Procrastinator Over a year ago

If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

Ankit Agrawal · Accepted Answer · 2020-08-07 18:26:22Z

-1

AS the name of exception suggest, there is issue in connection between your chromedriver and chrome browser.

Upgrade chrome browser to 84 and then retry or you can also download downgraded version of chromedriver which is compatible with your version of chrome.

answered Aug 7, 2020 at 18:26

Ankit Agrawal

2571 silver badge12 bronze badges

3 Comments

Mythreyi R. Over a year ago

I saw this suggestion on a few pages and upgraded my chrome driver accordingly. But the exception still occurs even though my browser and chrome driver are compatible versions (both are version 84). Is there anything else I can check or modify to avoid this exception?

Ankit Agrawal Over a year ago

Try these two checks and let me know if it resolves issue 1. see if your chromdriver is not left open. i think you should not get this issue on using driver.quit() 2. if you are still getting error, also check selenium-java version used in project. Make sure its latest stable version

Uday Over a year ago

not getting this issue in driver.quit(), but getting this issue in driver.close(), i have latest drivers too.

Abhinav Pandey · Accepted Answer · 2022-07-05 12:23:36Z

-2

I was also getting same error but it was resolved after changing selenium version.

answered Jul 5, 2022 at 12:23

Abhinav Pandey

1

2 Comments

ethry Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Japhei Over a year ago

This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From Review

Collectives™ on Stack Overflow

java.net.SocketException: Connection reset on Selenium driver.close() or driver.quit() statements

3 Answers 3

1 Comment

3 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

3 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related