Johannes Rudolph
Johannes Rudolph
This is likely a leak in `ProtocolSwitch` where not all substreams are closed before the stage is terminated. This seems to be fixed with Akka 2.6.x which automatically closes all...
Let's not fix this right now as Akka 2.5 itself is not really supported any more. We can keep the ticket open until we reach 10.3 where we will drop...
Investigation branch: https://github.com/akka/akka-http/compare/main...jrudolph:3963-try-to-harden-protocolswitch
@raboof, anything we could to about that?
Tried that with the fixes in https://github.com/akka/akka/pull/29121. It seems while it just hangs in the current version, with the fix, it will close the connection properly. The request will then...
> It seems for these kinds of errors TLSActor currently calls `fail(ex, closeTransport = false)` which means only cancellation is sent but no error. Not sure why that's the case....
Did you test on JDK 11? Would we expect it to succeed with the fix not yet released on 2.5.x?
Can now be restested with an update to 2.5.32.
Rebased on master where on JDK 11 it doesn't fail anymore with a timeout but now with the wrong exception because it seems the connection reset is received as a...
> Rebased on master where on JDK 11 it doesn't fail anymore with a timeout but now with the wrong exception because it seems the connection reset is received as...