Return-Path: Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org Received: (qmail 49854 invoked from network); 29 Nov 2005 22:28:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Nov 2005 22:28:20 -0000 Received: (qmail 65985 invoked by uid 500); 29 Nov 2005 22:27:48 -0000 Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org Received: (qmail 65861 invoked by uid 500); 29 Nov 2005 22:27:47 -0000 Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "HttpClient Project" Reply-To: "HttpClient Project" Delivered-To: mailing list httpclient-dev@jakarta.apache.org Received: (qmail 65838 invoked by uid 99); 29 Nov 2005 22:27:47 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2005 14:27:47 -0800 Received: by ajax.apache.org (Postfix, from userid 99) id 892FFDE; Tue, 29 Nov 2005 23:27:26 +0100 (CET) From: bugzilla@apache.org To: httpclient-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 37697] - console spam during connection errors from HttpMethodDirector w/java.util.logging X-Bugzilla-Reason: AssignedTo Message-Id: <20051129222726.892FFDE@ajax.apache.org> Date: Tue, 29 Nov 2005 23:27:26 +0100 (CET) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=37697 ------- Additional Comments From odi@odi.ch 2005-11-29 23:27 ------- Patrick, Please feel free to reopen and make suggestions by submitting a patch how you figure the logging could be improved. Please do also understand configuring logging is not fixing our code, since it works as desired. As I understand you are not shipping log configuration with your product. In my opinion this is not a good idea at all. Configuration is part of your product and should be shipped as such. In case you do not know, even JDK 1.4 is configurable at runtime. So there is no need for the end user to edit configuration files in her JRE installation. There is also no need that log output of HttpClient goes to the console. You can configure logging the way that HttpClient output goes to a file (good if you want to troubleshoot a user problem) or that no output is generated at all (good if you don't care). Please also understand that there is no such thing as a default configuration (the Java language specs do not define one). What is default with Sun's JDK may be different in IBM's JDK. And what Sun uses as defaults today can change tomorrow. The defaults of java.util.logging are different from other logging utitlies. It would be pointless to assume any defaults. Consider not configuring logging a programming error. This is especially true for Log4J, where not configuring logging leads to severe performance problems actually. Sorry I have no better news for you. Ortwin Gl�ck -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org