jgaalen commented on issue #6330: URL: https://github.com/apache/jmeter/issues/6330#issuecomment-2621294361
> > the problem is in httpclient4, where it is not actively closing the socket/responding to the FIN/ACK. It knows it is there > > Please double-check. The Java side does **not** know there's FIN. "FIN" is not exposed in Java APIs. If you know an API, please clarify which one exposes "FIN from the server". > > Then, the application (e.g. Java application) can't tell if the server "died completely", "fully closed the stream" or "closed the write part of the stream only". See [golang/go#67337 (comment)](https://github.com/golang/go/issues/67337#issuecomment-2123284523) If it doesn't know it received the FIN, how is it possible it sends the FIN back AFTER the httpclient4.validate_after_inactivity timeout? This is not the OS, it is the client (jmeter/java/httpclient) that does this -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
