Re: [DBCP] unnecessary logging.

[Dirk Verbeeck]

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
([EMAIL PROTECTED])
   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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]