Awhile ago I mentioned that we have an issue where the following will happen to a single request out of millions and millions. The message is sent by httpclient. Server receives the message. Server (claims to) send the response. Httpclient never sees it again.
Even with the socket timeout set to minutes the response never makes it to the client. Then we get a Socket timeout exception: read timed out. I asked if it was possible to keep track of open connections and if any particular thread was still active after XXX amount of time then be able to call some custom code. That way we can possibly inspect the running VM and not just logs after it has happened. Oleg, you said that it wasn't really possible with httpclient 3 but it is with 4 and I've since been able to upgrade to 4.. What did you have in mind that would allow me to do this? -k This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
