Excellent.
I just read the jira.. Since I'm on 4.0.x, when you say "For 4.0.x the problem can be worked around by retaining the pool lock for the entire span of the #closeIdleConnection." Is that something that I can do in my code, or will it require me to patch 4.0.x? Bear with me as I don't have the code open in front of me. -k -----Original Message----- From: Oleg Kalnichevski [mailto:[email protected]] Sent: Wednesday, June 02, 2010 7:21 AM To: HttpClient User Discussion Subject: RE: java.lang.IllegalStateException: Connection already open On Mon, 2010-05-31 at 22:39 -0400, Brooks, Kenneth S wrote: > I would love to but its pretty unlikely that I'll be able to do it.. we see 1 > or 2 of these in a 24 hour period. > There are millions of calls to the server during that time but that is spread > out among 16 (or more) client machines that are generating the load. > > I just realized that I misguided you a bit.. the server side is solaris10.. > the client side is windows (which is where httpclient is running) > I'll have to validate at work tomorrow if it is XP or something else. > > > The only thing I can do is get them to possibly ramp up the volume from a > particular machine to see if it makes the issue show up quicker. > > -k > Hi Ken I think I have found a cause of the problem https://issues.apache.org/jira/browse/HTTPCLIENT-948 Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] 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.
