On Thu, 2026-01-08 at 15:48 +0000, Vardin. Angel wrote: > Hello, > > I enabled the HttpComponents Client 5.5 logs to show DEBUG and TRACE > output for the package "org.apache.hc.client5.http.impl.io" in order > to get detailed HTTP/1.1 I/O information. > > During testing, I noticed that when the log severity is set to DEBUG, > many log entries appear that would ideally belong at the TRACE level. > For example, the logs were flooded with the following entry, which > provides very limited information: > > https://github.com/apache/httpcomponents-client/blob/master/httpclient5/src/main/java/org/apache/hc/client5/http/impl/io/PoolingHttpClientConnectionManager.java#L606 > > I also reviewed the codebase and could not find many TRACE-level log > statements. > > Is there any plan to improve the logging granularity in the future? >
No, there are no such plans. The verbosity and granularity of logging is subjective and we cannot please everyone. TRACE priority is not being used mostly because it is not consistently supported by all logging frameworks and back-ends. Regarding the example referenced above, this is actually a pretty bad case because if your code calls #closeExpired method more often than once a minute, something is very wrong. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
