| From: | "Neil Murray" <nhm(at)mimecast(dot)net> |
|---|---|
| To: | "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>, <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: jdbc pooling question |
| Date: | 2004-01-11 20:31:23 |
| Message-ID: | 01d001c3d881$e6af8830$020ba8c0@NOTEBOOK2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> We're suffering (probably) a connection leak problem while
> using Jdbc2PoolingDataSource that comes with jdbc drivers
> for postgres 7.3.
I posed a similar question to the forum a couple of weeks back and got no
answer. I have similar problems, but my biggest bugbear is the fact that the
Jdbc3PoolingDataSource (I use the JDBC3 drivers) does not throw any timeout
exception if you use getConnection() and there are no available connections
in the pool. The reason why there are no connections left in the pool is a
matter I need to investigate further, but I could be experiencing a similar
problem to you.
My team is working on our own connection pool - which will provide a bit
more transparency.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-01-11 21:02:41 | Re: setFetchSize |
| Previous Message | Marcus Andree S. Magalhaes | 2004-01-11 19:41:53 | jdbc pooling question |