Hi Oleg, please find attached a client log including wire logs as well as org.apache.commons.httpclient.HttpMethodDirector on DEBUG level.
In the log pattern you find a unique request id in brackets just next to the thread name. This can be used to easily correlated request/response pairs. At the beginning you find a request which encounters a Connection reset which the HttpMethodDirector retries. Request id is [e8b9b677-2451-477f-aef7-b41d86ccf2bd]. The retried request succeeds and receives a response. Another request with id [df776149-976e-444b-b7b7-b7148d9847ea] is a working example (request/response), no retry. Request with id [6ce80d68-56f9-4829-829a-ad54410f2bc5] is an example of a request with no retry and no reply which pops up at the client-side as an error. Reason: Method retry handler returned false. Automatic recovery will not be attempted The problem is although I think I understand what happens on the client-side I'm still not sure where and how to look for the actual cause of the problem. Acording to the current test results it looks like the requests do not reach the Synapse nodes. So maybe the HWLB closes the connection for some reason? Any help how to best proceed with the analysis is greatly appreciated. Regards, Eric > -----Original Message----- > From: Hubert, Eric [mailto:[email protected]] > Sent: Thursday, June 10, 2010 8:51 AM > To: HttpClient User Discussion > Subject: RE: Understand cause and properly handle Connection reset > > Hi Oleg, > > > I would be much easier to troubleshoot the problem if you managed to > > reproduce it with HttpClient 4.x. We effectively stopped maintaining > > HttpClient 3.1. > thanks for your reply. I forgot to mention one important point about why > we are using HttpClient 3.0.1 shipped with JBoss and haven't switched to > HttpClient 4.x yet. > > HttpClient is not always used directly but as part of the also frozen > XFire 1.2.6. For some other reasons we are currently tied to it. As there > will be no development on this end, we would also be willing to patch > XFire 1.2.6 to use HttpClient 4.x if there is a compelling reason to do > so. > > > > Anyways, could you please post a wire log of the HTTP session that > > exhibits the problem and a complete exception stack trace? It would be > > helpful to know at which point in the request execution process the > > connection reset takes place. > Sure I'll send a wire log as well as a complete stacktrace later today. > > Thanks, > Eric
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
