Hello, There are some parts of the code that use printStackTrace in order to show errors. It means that it's difficult to have control on how log will be produced. Those stacks will mainly go to application server logs and not directly into application logs if an application server is used (like tomcat, Jboss, ..). That's why I suggest to use logging API, like other libraries
I have posted an issue in Jira POOL-266 ( https://issues.apache.org/jira/browse/POOL-266). Phil Steitz added a comment on the issue (Today 21:1) "The reason that we don't use a logging API is to avoid introducing a dependency. If we do go that route, we should be consistent with DBCP and use commons-logging. I am not sure we really want to go this way, though. I am more inclined to support the suggestion in POOL-267. It would be better to discuss these things on the commons dev mailing list." Regards, Anthony Communier
