commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhusudan Pagadala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-4) [dbcp] Use commons-logging for debugging instead of System.out.println
Date Fri, 02 Nov 2007 18:57:50 GMT

    [ https://issues.apache.org/jira/browse/DBCP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539666
] 

Madhusudan Pagadala commented on DBCP-4:
----------------------------------------

This is very very important to change to commons-logging, also I prefer to add some more debug
or info statements like, creating new connections and closing old connections, and properties
used by the pooling, this type of logging should be there to optimize DB connections in pools,
and debug the production problems, this package is causing vey annoying because of there is
no logging, EVEN I AM THINKING OF OWNING COPY OF DBCP SOURCE and ADD LOGGING, finally Decided
to raise this as an issue, with fouram, I also created a JIRA, but this seems already sheduled
to 1.3, It will be very nice, THIS MESSAGE NOT ONLY MINE, IN MY OFFICE NEARLY 100 DEVELOPERS
VOTED FOR THIS CHANGE, I AM SENDING YOU THIS MESSAGE BEHALF ALL OF THEM.

I AM STRONGLY SUPPORT THIS CHANGE WITH 100/100 PREIORITY.


Thanks,
Madhu.

> [dbcp] Use commons-logging for debugging instead of System.out.println
> ----------------------------------------------------------------------
>
>                 Key: DBCP-4
>                 URL: https://issues.apache.org/jira/browse/DBCP-4
>             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 
> "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.

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


Mime
View raw message