You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by TomohitoNakayama <to...@basil.ocn.ne.jp> on 2005/06/26 16:33:18 UTC

Trap of ConnectionPool in DERBY-273

Hello.

I was trapped in DERBY-273.

Implementing of waiting connection to be closed was done.
However , I found problem that connection obtained from DataSource object 
was not physically closed
when "-Dframework=DerbyNet" was specified and then waiting processing never 
finished.

It seems that DataSource class implemented in IBM Universal JDBC Driver was 
acting as connection pool and
connection was not closed even if close method was called ...
I surveyed DB2 site of IBM and could not found way to force DataSource to 
close pooled connection.


Now I think next 2 walk round.

walk round 1:
Kick garbage collection and encourage DataSource object to close pooled 
connection,
though execution of gc is not guranteed.

Concretely, set variable , which refers DataSource object , as null and 
execute System.gc().
This would encourage DataSource object to close pooled connection.

Using jdb, I saw this works in sun jdk 1.4.

walk round 2:
If connection was not closed after number of checks,
force shutdown.

We could expect needed rollback process would be finished.
In the worse case, test was just failed.


If there are some any other idea, please advise me.


Best regards.


/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
         tmnk@apache.org

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/ 



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.1/28 - Release Date: 2005/06/24


Re: Trap of ConnectionPool in DERBY-273

Posted by TomohitoNakayama <to...@basil.ocn.ne.jp>.
Hello.


I had considered about problem and walkround written in previous mail and 
reached a conclution
myself.

http://mail-archives.apache.org/mod_mbox/db-derby-dev/200506.mbox/%3c000301c57a5c$0186f990$0800a8c0@Arkat%3e

I concluded the walk round 1 and 2 were not good solution.
Instead , function to kill session is needed for this the problem.

I will continue DERBY-273 on that line.


On the other hand,
modify-2: written in
    http://issues.apache.org/jira/browse/DERBY-273
can be done separatedly.

I will make subtask for modify-2 and finish it first.


Best regards.


/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
         tmnk@apache.org

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- 
From: "TomohitoNakayama" <to...@basil.ocn.ne.jp>
To: "Derby Development" <de...@db.apache.org>
Sent: Sunday, June 26, 2005 11:33 PM
Subject: Trap of ConnectionPool in DERBY-273


> Hello.
>
> I was trapped in DERBY-273.
>
> Implementing of waiting connection to be closed was done.
> However , I found problem that connection obtained from DataSource object
> was not physically closed
> when "-Dframework=DerbyNet" was specified and then waiting processing
> never finished.
>
> It seems that DataSource class implemented in IBM Universal JDBC Driver
> was acting as connection pool and
> connection was not closed even if close method was called ...
> I surveyed DB2 site of IBM and could not found way to force DataSource to
> close pooled connection.
>
>
> Now I think next 2 walk round.
>
> walk round 1:
> Kick garbage collection and encourage DataSource object to close pooled
> connection,
> though execution of gc is not guranteed.
>
> Concretely, set variable , which refers DataSource object , as null and
> execute System.gc().
> This would encourage DataSource object to close pooled connection.
>
> Using jdb, I saw this works in sun jdk 1.4.
>
> walk round 2:
> If connection was not closed after number of checks,
> force shutdown.
>
> We could expect needed rollback process would be finished.
> In the worse case, test was just failed.
>
>
> If there are some any other idea, please advise me.
>
>
> Best regards.
>
>
> /*
>
>         Tomohito Nakayama
>         tomonaka@basil.ocn.ne.jp
>         tomohito@rose.zero.ad.jp
>         tmnk@apache.org
>
>         Naka
>         http://www5.ocn.ne.jp/~tomohito/TopPage.html
>
> */
>
>
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.8.1/28 - Release Date: 2005/06/24
>
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.8.1/28 - Release Date: 2005/06/24
>
>



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.5/32 - Release Date: 2005/06/27