RFR: 8293562: blocked threads with KeepAliveCache.get [v3]

Jaikiran Pai jpai at openjdk.org
Wed Sep 28 14:03:24 UTC 2022


On Tue, 27 Sep 2022 19:00:28 GMT, Daniel Jeliński <djelinski at openjdk.org> wrote:

>> Please review this patch that makes sure KeepAliveCache does not block all threads while closing sockets.
>> 
>> Changes:
>> - get operation no longer closes sockets; if there's no socket that is recent enough, get returns null and lets the cleaner thread close the sockets
>> - put operation closes sockets without holding the cache lock. Additionally, if the cache is full, it places the new connection in the cache and removes the oldest connection.
>> - the cleaner thread creates a list of connections to close, and then closes them after releasing the cache lock
>> - additionally, we set the socket timeout to 1 millisecond before calling socket.close
>> 
>> The new test fails with `Wait for second request timed out` without this patch, passes after the changes. Tiers 1-3 clean.
>
> Daniel Jeliński has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Stop using getLocalhost

src/java.base/share/classes/sun/net/www/http/KeepAliveCache.java line 275:

> 273:             }
> 274:             // close connections outside cacheLock
> 275:             if (closeList != null) {

Should we perhaps move this entire `if` block inside the `finally` just after the call to `cacheLock.unlock()`. That way even if there was any exception in that loop, then we wouldn't end up losing and thus leaking these unclosed sockets?

-------------

PR: https://git.openjdk.org/jdk/pull/10401


More information about the net-dev mailing list