RFR: 8371903: HttpClient: improve handling of HTTP/2 GOAWAY frames with error code [v10]

[EunHyunsu]

On Mon, 12 Jan 2026 06:15:59 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

>> @djelinski   
>> I addressed the deadlock by moving `close(cause)` outside of stateLock, keeping the stream iteration synchronized while avoiding holding the lock during `close()`.
>> 
>> The change works in local testing, but I don’t have a way to validate this under CI conditions. I’m also unsure whether this is the best solution, so I’d appreciate any guidance or alternative suggestions.
>
> Hello @ehs208, looking at these issues, I think this might need a bit more work and I don't have a straightforward/easy suggestion to make right now and I will need to take a deeper look at the code and experiment with a few changes. Would it be OK, if I took over the work on this one? I will add you as a contributor for the help you have provided so far.

@jaikiran I see @dfuch suggested using AtomicLong to store lastProcessedStream at the connection level. Should I try implementing this approach, or would you prefer to handle it since you're taking over the work?

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

PR Comment: https://git.openjdk.org/jdk/pull/28632#issuecomment-3758290122