DO NOT REPLY [Bug 29973] New: - HttpClient wire log performance problems

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29973>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29973

HttpClient wire log performance problems

           Summary: HttpClient wire log performance problems
           Product: Commons
           Version: 2.0 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: HttpClient
        AssignedTo: commons-httpclient-dev@jakarta.apache.org
        ReportedBy: wim.bervoets@axa.be


Hi,

My application is using HttpClient. We have experienced a serious slowdown when 
no HttpClient specific log4j settings are set in a log4j.properties file. Eg:

If we add: 

# Disable debug HttpClient wire logging
log4j.category.httpclient=ERROR, R
log4j.category.httpclient.wire=ERROR, R
log4j.category.org.apache.commons=ERROR, R 

then our pdf is sent back in around 700ms. If we remove the above settings then 
it sometimes (depending on the load of the server) took around 2 minutes to 
send the same pdf back. 

It appears that HttpClient is creating a lot of wire logs in memory if you 
don't specify log4j settings and at the end sees that it actually doesn't have 
to log it to file/console,...

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