You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2003/08/28 00:21:46 UTC
DO NOT REPLY [Bug 22776] New: -
DBCP should not be writing messages to stderr or stdout
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22776>.
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).