commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22776] New: - DBCP should not be writing messages to stderr or stdout
Date Wed, 27 Aug 2003 22:21:46 GMT
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).

Mime
View raw message