On Fri, 28 Aug 2026 14:58:35 GMT, Daniel Fuchs <[email protected]> wrote:
>> b4dc8c03a6c introduces further checks for idleness. >> >> I've reverted the `volatile` copy, since it is only read & written while the >> lock is held. >> >>> I guess that your reasoning was that the event would eventually fire and >>> terminate the connection later? So your concern was just to prevent it from >>> being reused? >> >> Correct. > > The field is still volatile - so we should read it only once. Introduced `volatile` copy again in f4165d33a61. Assuming you don't have further remarks on b4dc8c03a6c, resolving this conversation. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/32545#discussion_r3892911795
