Community
Participate
Working Groups
With the migration to the new HTTP transport the Hudson connector started logging a lot of output to the console by default: 16:29:24.517 [pool-1-thread-28] DEBUG org.apache.http.headers - << Keep-Alive: timeout=15, max=100 16:29:24.517 [pool-1-thread-28] DEBUG org.apache.http.headers - << Connection: Keep-Alive 16:29:24.517 [pool-1-thread-28] DEBUG org.apache.http.headers - << Content-Type: text/plain 16:29:24.518 [pool-1-thread-28] DEBUG o.e.m.c.r.h.core.CommonHttpClient$1 - Connection can be kept alive for 15000 MILLISECONDS 16:29:24.518 [Worker-51] DEBUG o.a.h.i.c.t.ThreadSafeClientConnManager - Released connection is reusable. 16:29:24.518 [Worker-51] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - Releasing connection [HttpRoute[{s}->https://hudson.eclipse.org]][null] 16:29:24.518 [Worker-51] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - Pooling connection [HttpRoute[{s}->https://hudson.eclipse.org]][null]; keep alive for 15000 MILLISECONDS 16:29:24.518 [Worker-51] DEBUG o.a.h.i.conn.tsccm.ConnPoolByRoute - Notifying no-one, there are no waiting threads ...
Moved logging initialization into new method CoreUtil.initializeLoggingSettings() which is invoked early in HttpUtil.
Created attachment 209940 [details] mylyn/context/zip