RFR: 8358496: Concurrent reading from Socket with timeout executes sequentially [v2]
Daniel Fuchs
dfuchs at openjdk.org
Tue Jun 3 16:24:56 UTC 2025
On Tue, 3 Jun 2025 16:10:38 GMT, Alan Bateman <alanb at openjdk.org> wrote:
>> If several threads attempt to read from a Socket's input stream at the same time then all but the winner will block trying to acquire the read lock. This is okay for untimed-reads but surprising for timed-reads as the timeout is only effective after acquiring the lock. The SocketImpl is changed so that the timeout applies to the total time waiting to acquire and read.
>>
>> A new test is added to the existing java/net/Socket/Timeouts test. It is migrated from TestNG to a JUnit test as a drive-by change - it's mostly mechanical and the changes kept as minimal as possible.
>
> Alan Bateman has updated the pull request incrementally with one additional commit since the last revision:
>
> Make test comment cleaner
Marked as reviewed by dfuchs (Reviewer).
-------------
PR Review: https://git.openjdk.org/jdk/pull/25614#pullrequestreview-2893258189
More information about the net-dev
mailing list