I solved it. The problem was that when I got up to around 70 or 80
concurrent connections, the database server had too many files open. I
added lines in rc.local to increase /proc/sys/fs/file-max and
/proc/sys/fs/inode-max fourfold, and since then I've been up to almost
120 concurrent connections with no problem.
I had started running a large new webapp about a week ago and I
drastically underestimated the effect it would have. The number of
pages I'm serving per hour sextupled from one week to the next. The
number of concurrent database connections seems to have nearly tripled.
Not to mention the number of calls I get per day...
thanks,
ben
On Tuesday, January 8, 2002, at 04:37 PM, Tom Lane wrote:
> bcarterette@mail.liberty.k12.mo.us writes:
>> I am running several databases on a PostgresQL server and webapps to go
>> with them on another server. For the past couple of days, several
>> times
>> a day I've been getting a "The backend has broken the connection.
>> Possibly the action you have attempted has caused it to close." error.
>> When this happens, all connections close and anyone in the middle of a
>> session is screwed.
>
> Sounds like you are seeing backend crashes. Does the postmaster log
> show any complaints about unexpected child process exits? Are there
> any core files laying about in the database subdirectories? Ideally
> I'd like to see a debugger backtrace from a core file ...
>
> In any case, this is not a Java or JDBC problem, it's a backend problem.
>
> regards, tom lane
>
