On Sat, 2012-03-10 at 17:53 -0500, Greg Lindholm wrote: > Is there anything from the http get or the response objects I could log that > might throw some light on what is happening?
Please have a look at the HttpClient logging guide: http://hc.apache.org/httpcomponents-client-ga/logging.html Oleg > Is there anyway to get at the raw message exchange after-the-fact once I've > gotten the response? Maybe a custom subclass of httpget? > > Again, any help would help. > > Thanks > Greg > > > Sent from my iPad > > On Mar 10, 2012, at 3:10 PM, Oleg Kalnichevski <[email protected]> wrote: > > > On Fri, 2012-03-09 at 15:17 -0500, Greg Lindholm wrote: > >> I have a web app that uses HttpClient 4.1.3 and HttpCode 4.1.4 to send a > >> request to another service I also run and the client is getting occasional > >> status codes 505 and 400 reported. > >> > >> It processes about 50,000 requests a day and in each days log I see 25 - 50 > >> errors for unexpected status codes of either 505 or 400 being returned. > >> > >> My service is running under Tomcat 6 and it doesn't (in my code) ever > >> return a status 400 or 505, and there is nothing in the service logs to > >> indicate a problem. (It's possible if there was a problem at the service > >> that I'm not logging it.) > >> > >> When my app gets one of these unexpected status code I dump everything > >> about the transaction to the log but I am not seeing anything odd, > >> everything I see is looking fine. > >> > >> The client is using ThreadSafeClientConnManager and DefaultHttpClient and > >> it's executing an HttpGet always to the same URL with some Headers added. > >> > >> I have not been able to reproduce this issue in testing only in production. > >> > >> Is there any know issues that would cause this? > >> > >> Can anyone suggest how to figure out what is causing this? > >> > > > > There is no way of saying for sure without seeing the exact message > > exchanges. HTTP status 505 (HTTP version not supported) seems bizarre > > though. > > > >> Is ThreadSafeClientConnManager really thread safe? > > > > Yes, it is. > > > >> Is DefaultHttpClient created with a ThreadSafeClientConnManager thread > >> safe? > >> > > > > Yes, it is. > > > > These problems are unlikely to have anything to do with thread safety. > > > > Oleg > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
