| From: | "Jordan S(dot) Jones" <jordanj(at)racistnames(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Odd Connection Issues |
| Date: | 2003-04-02 10:07:47 |
| Message-ID: | 3E8AB673.7050600@racistnames.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hello,
I am in the process of writing a client/server application that uses
PostgreSQL as the database backend. I am expecting a high amount of
traffic through this server, so I have opted to utilize the
Jdbc3PoolingDataSource class to get my connections from.. When the
server starts up, it creates, at this point, an initial pool fof 50
connections and a max of 75. The problem I am running into, is after
236 connections, it hangs on dbPool.getConnection (); where dbPool = new
Jdbc3PoolingDataSource (); From what I have seen, it never returns from
this state.
Previously, this behavior would occur around 255 connections. I am
using 7.3.2..
Any help on the matter would be greatly appreciated.. If this isn't at
all coherent, I sincerely apologize.
Thanks,
Jordan S. Jones
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Laban | 2003-04-02 14:49:27 | Changing transaction isolation mid-transaction |
| Previous Message | Jordan S. Jones | 2003-04-02 10:02:49 | Odd Connection Issues |