Jon, I think I found it out. We had a short timeout on our responses and so we were seeing 504s being generated by the client when that timeout was reached.
Thomas On Mon, Nov 21, 2011 at 6:36 PM, Jon Moore <[email protected]> wrote: > Hi Thomas, > > Are you using the caching module (CachingHttpClient)? If so, there are > certain cases where the cache is required to return 504 responses if > it can't talk to the origin. Since you're making a large number of > concurrent requests, it's possible the origin is being overloaded. > Another question is whether there is a proxy (e.g. Squid/Varnish) > between your client and origin--if so, it could be the source of the > 504s for the same reason. > > Can you post a wire log showing some of the successful and > unsuccessful responses? > > http://hc.apache.org/httpcomponents-client-ga/logging.html > > Jon > > On Mon, Nov 21, 2011 at 6:51 PM, Thomas Van de Velde > <[email protected]> wrote: > > Hi, > > > > We are seeing 504 error response being received by the client but none > > appeared in the server logs. Is it possible that the httpclient is > return a > > 504 instead of the server? If so, what can we do to tune the client? We > are > > making a large number of concurrent http requests. > > > > Thanks, > > Thomas > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
