From: | "John Sidney-Woollett" <johnsw(at)wardbrook(dot)com> |
---|---|
To: | "Neil Murray" <nhm(at)mimecast(dot)net> |
Cc: | "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-12 08:01:56 |
Message-ID: | 2101.192.168.0.64.1073894516.squirrel@mercury.wardbrook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Have you tried looking at the Apache db connection pool? See
http://jakarta.apache.org/commons/dbcp/
It might save you some time and effort.
John Sidney-Woollett
Neil Murray said:
>> 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.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Keith C. Klopfer | 2004-01-12 08:32:24 | Weird ILIKE behavior: Solved |
Previous Message | Keith C. Klopfer | 2004-01-12 07:36:09 | Weird ILIKE behavior |