ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashok Madhavan <ashok.madha...@gmail.com>
Subject Re: FW: Connection Closing Problem
Date Wed, 03 Jun 2009 01:43:16 GMT
Hi,in apache dbcp did u set the following properties:
    <property name="removeAbandoned"><value>true</value></property>
    <property name="removeAbandonedTimeout"><value>1</value></property>
    <property name="logAbandoned"><value>true</value></property>

http://commons.apache.org/dbcp/configuration.html.<http://commons.apache.org/dbcp/configuration.html>
look for 'removeAbandoned'.

regards
ashok

On Wed, Jun 3, 2009 at 2:32 AM, Nicholoz Koka Kiknadze
<kiknadze@gmail.com>wrote:

> I think what happens to open (pooled) connection upon JVM exit depends on
> JDBC driver.
>
> IMO if you were using SimpleDataSource of iBatis, you'd have to call
> forceCloseAll() to close all pooled connections at the end of execution of
> your app (I think I have even used that years ago).  Not sure about DBCP,
> but I bet  calling  basicDataSource.close() must help.
>
> GL
>
>
> On Wed, Jun 3, 2009 at 12:18 AM, Nathan Modrzewski <
> nmodrzewski@eaglexm.com> wrote:
>
>>  Not yet…getting ready too.
>>
>>
>>
>> If I’m using Apache Dbcp to handle connection pooling, do I have to
>> manually close the pooling objects?
>>
>>
>>
>>
>

Mime
View raw message