Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 48092 invoked from network); 27 Aug 2003 22:18:56 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 27 Aug 2003 22:18:56 -0000 Received: (qmail 21196 invoked by uid 50); 27 Aug 2003 22:21:46 -0000 Date: 27 Aug 2003 22:21:46 -0000 Message-ID: <20030827222146.21195.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22776] New: - DBCP should not be writing messages to stderr or stdout X-Spam-Rating: daedalus.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=22776 DBCP should not be writing messages to stderr or stdout Summary: DBCP should not be writing messages to stderr or stdout Product: Commons Version: Nightly Builds Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Dbcp AssignedTo: commons-dev@jakarta.apache.org ReportedBy: shankar@cotagesoft.com DBCP should not be writing messages to stderr or stdout. It should be using commons-logging to log stuff. The current irritant is the message written to stderr from AbandonedObjectPool's constructor. But the AbandonedLog is also important to capture in the application's log, not lost to stderr (without a timestamp or anything).