Hi all,
Following up This turned out to be a red-herring , the threads that were connecting were getting on and off the socket so fast that the thread dump always showed that the connection was in the state of being locked. I had to move one step deeper into the code and look at the loop that was creating the connection and fix the problem there. Thanks, Jim /////////////////////////////// Jim Langston Technical Consultant [email protected] (313) 227-0407 (Office) (513) 702-4741 (Cell) From: Langston, Jim [mailto:[email protected]] Sent: Monday, April 18, 2011 3:33 PM To: HttpClient User Discussion Subject: RE: Locking problems of SocketInputSteam at org.apache.commons.httpclient.HttpParser.readRawLine Thanks Oleg, I have been reading up on some of the other responses, not sure why your email didn’t come through correctly, but I did see the response in the archive. soTimeout is set to 30000 ConnectionTimeout is set to 5000 Hitting the site from the browser, I never get any timeouts, it will sit with the dialogue box active. As soon as I hit the dialogue, the site will continue on. It can be 1 min or 2 days. I was going to attempt to fix it in the app, but I don’t know if I can, tomcat shows the thread active, even if I stop/kill the browser session. I need to restart tomcat to clear it. Jim ////////////////////////////////// Jim Langston Technical Consultant [email protected] (313) 227-0407 (Office) (513) 702-4741 (Cell) The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. From: Oleg Kalnichevski [mailto:[email protected]] Sent: Monday, April 18, 2011 3:10 PM To: HttpClient User Discussion Subject: RE: Locking problems of SocketInputSteam at org.apache.commons.httpclient.HttpParser.readRawLine
