From: | "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | jdbc pooling question |
Date: | 2004-01-11 19:41:53 |
Message-ID: | 61543.200.174.148.100.1073850113.squirrel@webmail.webnow.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi, guys.
We're suffering (probably) a connection leak problem while
using Jdbc2PoolingDataSource that comes with jdbc drivers
for postgres 7.3.
Recently, a freeze problem was detected and the debugging
showed that we may have some leaks.
Before digging deeply into the driver's source code, we decided
to analyze our own java sources and found a couple places where
the statements and the connections were closed, but not the
resultset.
The question is, in this configuration (connection & statement closed),
there is any possibility of the connection isn't being properly closed
by the pool and, therefore, being leaked?
thanks in advance.
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Murray | 2004-01-11 20:31:23 | Re: jdbc pooling question |
Previous Message | Ramin Rad | 2004-01-11 18:32:50 | JDBC parse error with preparedStatement! |