[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-user
Subject:    Re: [DBCP] unnecessary logging.
From:       Dirk Verbeeck <dirk.verbeeck () pandora ! be>
Date:       2003-12-22 13:47:52
[Download RAW message or body]

In a normal production environment it isn't recommended to rely on the 
abandoned feature to recover from connection leaks. All connections 
should be closed by your code. This removedAbandoned option should 
only be enabled to debug connection leaks and/or as a temporary 
workaround.

The printed message is a warning and cannot be disabled.
(unless you remove the message in the DBCP source and recompile)

-- Dirk

Antony Paul wrote:
> Hi,
>   I am using DBCP 1.1 with Tomcat 4.1.27. I am getting this message in the
> stdout frequently. Why this is printing. How to disable it.
>   AbandonedObjectPool is used
> (org.apache.commons.dbcp.AbandonedObjectPool@1a44d6)
>    LogAbandoned: true
>    RemoveAbandoned: true
>    RemoveAbandonedTimeout: 30
> 
> This is portion of DBCP configuration.
> <parameter>
>   <name>removeAbandoned</name>
>   <value>true</value>
>  </parameter>
>  <parameter>
>   <name>removeAbandonedTimeout </name>
>   <value>30</value>
>  </parameter>
>  <!-- remove from production deployment performance overhead  -->
>  <parameter>
>    <name>logAbandoned</name>
>    <value>true</value>
>  </parameter>
> 
> rgds
> Antony Paul.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
> 
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]