I'm encountering issues with large SOAP response payloads using the http-hc5 AsyncHTTPConduit. It seems the stream-reader encounters an unexpected EOF while processing the stream. The issue is not reproducible with the http-hc AsyncHTTPConduit. Test-cases are linked below.
I've also monitored the existing AsyncHTTPConduitTest with wireshark in both modules http-hc and http-hc5. While http-hc behaves as you'd expect, http-hc5 produces RST,ACK (reset) instead of the expected FIN,ACK, even when processing is seemingly successful. Attached a couple of screenshots to illustrate.
Unfortunately I've not been able to pinpoint what the cause of the issue is. This has happened using three different backends, jetty, undertow and some ancient SOAP production system that I'm sure are running neither of those, so it seems the issue is at least on the client-side.
Fails with http-hc5, succeeds with http-hc.
Please let me know if you need me to provide any further details.