... > >> Why are there 3 copies of the same log message? > > > > There are several places where HttpConnection#close or #shurdown are > > called in the course of exceptional execution flow. The logging can be > > changed though so that only the first invocation is logged. > > Can it be changed so that the original cause is logged? >
Generally HttpClient uses log or re-throw policy on exception propagation. It never logs exceptions if it propagates them to the caller. If exception is retried and not propagated it is always logged. > >> And why is the connection being closed? > >> The timestamp shows it happens immediately - there is probably not > >> time to actually contact the remote host. > >> > >> The same sequence repeats another 3 times (there are 6 loops on the > >> test, alternate ones - 2,4,6 - fail on this one sample) > >> All other samples in the test work OK as far as I can tell. > >> > >> Any ideas how to debug this further? > >> > > > > Could you please post the complete log (obfuscated if necessary) or > > attach it to the ticket? > > It's quite long, and repetetive, and there's potentially a lot to > redact before I can post it in a public place > Would it be easier for you to create a reproducer (preferably a JUnit)? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
