From: | Glenn Holmer <gholmer(at)weycogroup(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: too many clients |
Date: | 2003-11-04 15:03:20 |
Message-ID: | 3FA7BFB8.3050906@weycogroup.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Paul Thomas wrote:
>
> On 04/11/2003 13:34 Glenn Holmer wrote:
>
>> 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.
>>
>
> You've probably reached max_connections. Try upping the value in your
> postgresql.conf. You'll need to restart the back-end for it to take effect.
This is on SuSE 8.2, which provides a file /etc/sysconfig/postgresql;
this is where we put "-i" for TCP/IP. Since that's a postmaster flag,
I'm probably OK with putting the max_connections here as well? Looks
like it would be, e.g. "-i -N 64 -B 128"? (space after -N and -B?)
There are a lot more Postgres users on this machine lately (some new
apps). A long time ago, we used to get "hash table out of memory.
Use -B parameter to increase buffers"; that param was never added when
we upgraded the machine last summer.
--
____________________________________________________________
Glenn Holmer gholmer(at)weycogroup(dot)com
Programmer/Analyst phone: 414.908.1809
Weyco Group, Inc. fax: 414.908.1601
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2003-11-04 15:03:51 | Re: DatabaseMetaData - getImportedKeys |
Previous Message | Nick Fankhauser | 2003-11-04 14:22:25 | Re: too many clients |