hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPCLIENT-1448) Add context information to DefaultRequestDirector INFO level logging
Date Fri, 17 Jan 2014 16:50:19 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski updated HTTPCLIENT-1448:
------------------------------------------

    Fix Version/s: 4.3.3

Tamas,
I wish I could just merge in your branch from the pull request, but I can't due to ASF legal
requirements. Could you please attach your changes as a patch to this ticket? Please also
note it is unlikely there will be any new releases from the 4.2.x branch, so may have to upgrade
to 4.3 in order to pick up this improvement from an official release.

Oleg

PS: Just out of curiosity, aren't you guys supposed to use AHC, like, everywhere at Sonatype?

> Add context information to DefaultRequestDirector INFO level logging
> --------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1448
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1448
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>            Reporter: Cservenak, Tamas
>            Priority: Minor
>             Fix For: 4.3.3
>
>
> In Nexus MRM HttpClient4x is used as transport. Nexus is a proxy server, hence there
is a lot of (independent) interaction of HttpClient4x with remote servers on behalf of incoming
requests. HttpClient does some INFO level logging that in my opinion lacks some context. Typical
example:
> {quote}
> 2014-01-14 12:31:17 INFO  [qtp1303027754-18064]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:31:17 INFO  [qtp1303027754-18064]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:31:21 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:31:21 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:31:28 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:31:28 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:31:40 INFO  [qtp1303027754-18053]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:31:40 INFO  [qtp1303027754-18053]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:31:47 INFO  [qtp1303027754-18060]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:31:47 INFO  [qtp1303027754-18060]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:32:02 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:32:02 INFO  [qtp1303027754-18036]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> 2014-01-14 12:32:18 INFO  [qtp1303027754-18059]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- I/O exception (org.apache.http.NoHttpResponseException) caught when processing request:
The target server failed to respond
> 2014-01-14 12:32:18 INFO  [qtp1303027754-18059]  org.sonatype.nexus.apachehttpclient.Hc4ProviderBase$DefaultHttpClientImpl
- Retrying request
> {quote}
> "Muting" the logger category or raising level to WARN is not an option, as we do not
want to "mute" whole HttpClient4x.
> This is emitted by DefaultRequestDirector at INFO level, but is merely a log-spam, as
it does not offer much information about actual host/target causing it.
> I'd propose to equip these messages with some technical and contextual information. Patch
will be provided in few.
> Note: another option would be to just "lower" these logs (or one of the two) to DEBUG
level, and leave the "Retrying request" part but with target host added.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message