You have exceeded your connection limit to the database. I believe it
defaults to 64 in most distributions. This is a general administration
issue- not specific to JDBC. All database clients, such as psql, pg_dump,
etc... draw from the same limited resource.
Your pooling applications are probably OK because they initially create a
set of connections that are never released- simply pooled & re-used.
You may be able to bring temporary relief by increasing your connection
limit in postgresql.conf, but the long term fix involves managing the
connections via pooling or other resource management schemes.
-Nick
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Glenn Holmer
> Sent: Tuesday, November 04, 2003 8:35 AM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] too many clients
>
>
> What does this mean and how do I diagnose it?
>
> java.sql.SQLException: FATAL: Sorry, too many clients already
>
> Not all the Postgres databases on this machine are experiencing this.
> One of them is using pooling with Tomcat and the JNDI interface.
>
> --
> ____________________________________________________________
> Glenn Holmer gholmer@weycogroup.com
> Programmer/Analyst phone: 414.908.1809
> Weyco Group, Inc. fax: 414.908.1601
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
>
