[DBCP-4] [dbcp] Use commons-logging for debugging instead of System.out.println

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Nightly Builds
• Fix Version/s: 1.3

Environment

Operating System: All
Platform: All

• Bugzilla Id: 30375
• Assignee: Unassigned
• Reporter: Alan Tam
• Created: 29/Jul/04 14:52
• Updated: 15/Feb/10 04:20
• Resolved: 18/Feb/09 16:49

Description

At the source code of commons-dbcp, some System.out.println() and
System.err.println() statements can be found, noticeably in the constructor of
"java.org.apache.commons.dbcp.AbandonedObjectPool".

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.

Issue Links

• is duplicated by: DBCP-200 Replace the System.outs with commons-logging