> now, given that i can confirm that i am closing connections (calling
close()
> on them, which returns them to the pool), can you suggest how i might
locate
> where those connections are not getting released? i have read some stuff
> about dbcp not being entirely reliable in releasing connections. is that
> true? argh.

One question. Why should DBCP *release* a connection?

The way I see it, DBCP is running fine. Let me explain.

The job of any JDBC connection pool is to open connections for you, to keep
a pool of pre-opened connection "ready to serve" and to manage it. Nobody
ever mentiones *closing* the connections. Well, they can be closed, usually
in two situations:

1. the number of unused connections is over the maxUnused
2. the pool has decided to "recycle" the connections (to clean up memory
leaks and garbage)

You are definitely not falling under (1) - heavy load of your site will
consumes more and more of the DB. You are most likely not a candidate for
(2), either - after 5 minutes no reasonable connection pool will consider
any particular connection "stale" or a "candidate for recycling to prevent
memory leaks".

So, again, why should you see connections being closed, if the load of oyur
site is growing?

OTOH, if you are using connections from the pool and returning them on
regular basis, then there shouldn't be an increase of numebr of open
connections. If you can verify this scenario, then you have located a bug:

1. count open connections
2. open a connection from the pool
3. do something
4. close a connection (this should return it to the pool)
5. repeat a number of times (10 loops, 100 loops, 1000 loops,...)

See what happens. This activity should not make any change in the number of
connections. The only thing you should expect is the recycling of
connections that I have mentioned, which would happen after some time or
after a numebr of uses.

Nix.


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

Reply via email to