commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] Resolved: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println
Date Wed, 18 Feb 2009 16:51:03 GMT


Mark Thomas resolved DBCP-4.

    Resolution: Fixed

Compromise patch applied.
- Logging to stdout on pool creation was removed as a generally bad idea and inconsistent
with the other pool impls
- Logging location of traces was made configurable. Developers using DBCP directly can change
the PrintWriter. App servers embedding DBCP (such as Tomcat) will probably need to retain
their mechanisms for handling libraries that use stdout.

> [dbcp] Use commons-logging for debugging instead of System.out.println
> ----------------------------------------------------------------------
>                 Key: DBCP-4
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: Nightly Builds
>         Environment: Operating System: All
> Platform: All
>            Reporter: Alan Tam
>            Priority: Minor
>             Fix For: 1.3
>         Attachments: dbcp-commons-logging-2.patch, dbcp-commons-logging.patch
> At the source code of commons-dbcp, some System.out.println() and
> System.err.println() statements can be found, noticeably in the constructor of 
> "".
> These statements are annoying, because none of the developers want to see these
> messages but they occuplied the precious space in the log files.
> I think it is still appropriate to use this method to emit errors, but for
> normal behavior, we should have an option never seeing them.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message