Re: JDBC techy pooling questions

In article <8f433h$1fr5_at_imsp212.netvigator.com>, "ct" <tam_at_asiaonline.net> wrote:

>My 2 cents. If a connection is never expired within the pool, your program
>may get
>an out of memory error. It seems that oracle thin driver does not release
>any resources
>even though your program closes all statement and resultset.
>
>Chris Tam
>

My connection pool takes and returns connections to and from the pool like a stack. This causes extra connections to sit idly at the bottom of the stack. A periodic task checks the "last used" time on the bottom of the stack and closes anything older than 10 seconds.

My problem is that there's a rare but possible chance I could loose all references to a Connection if there's an unexpected exception, like OutOfMemoryError. JDBC docs say it will be garbage collected but Oracle docs say it won't. I have found a solution, which I posted in another response. Received on Sun May 07 2000 - 00:00:00 CEST