Unless things changed in the last 1.5 years (when I looked it up last time): DBCP uses System.out.println() and not regular logging for the output of exactly those lines :(

Regards,

Rainer

Gregor Schneider wrote:
Hi guys,

we're using a JDBC-datasource with the following definition in
$CATALIN_HOME/conf/Catalina/localhost/IndexCLUE.xml:

<?xml version='1.0' encoding='utf-8'?>
<Context>
 <Resource
   auth="Container"
   description="DB Connection for CLUE-Index"
   name="jdbc/IndexCLUEDS"
   type="javax.sql.DataSource"
   factory="org.apache.commons.dbcp.BasicDataSourceFactory"
   driverClassName="com.mysql.jdbc.Driver"
   username="xxxx"
   password="xxxx"
   url="jdbc:mysql://db/index_clue?autoReconnect=true"
   maxIdle="30"
   maxWait="10000"
   maxActive="10"
   validationQuery="SELECT 1"
   testOnBorrow="true"
   testWhileIdle="true"
   timeBetweenEvictionRunsMillis="10000"
   minEvictableIdleTimeMillis="28800"
   poolPreparedStatements="true"
   removeAbandoned="true"
   removeAbandonedTimeout="300"
   logAbandoned="false"/>
</Context>

In catalina.out, we always find the following output:

AbandonedObjectPool is used ([EMAIL PROTECTED]
e)
  LogAbandoned: false
  RemoveAbandoned: true
  RemoveAbandonedTimeout: 300

I have no idea how to stop this, so can anyone of you guys give me a
clue where to look for to stop this output?

TIA

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to