PgSQL 9.1: Warning - error 10061 on Windows, no error on Linux - but connection is broken - Mailing list pgsql-general

From Edson Richter
Subject PgSQL 9.1: Warning - error 10061 on Windows, no error on Linux - but connection is broken
Date
Msg-id BLU0-SMTP44066E5D05B4448488881E8CF4D0@phx.gbl
Whole thread Raw
Responses Re: PgSQL 9.1: Warning - error 10061 on Windows, no error on Linux - but connection is broken
List pgsql-general
I just discovered a non PostgreSQL problem (but I was suspecting all the
time from PostgreSQL).

I'm recording this because would save lot of time from others in the
list, since my problem is already solved.

During this day, we had very busy servers and suddenly we started to get
error 500 and 502 on our Java server, after a select, update or insert.
- Looking web server logs shows no error.
- Looking PostgreSQL logs, in Windows server I saw error "winsock error
10061", but in Linux server I've found no evidence of the problem.

After digging for an hour, I've discovered our connection pool (max 100
connections, 50 idle) have been configured (probably by me) to drop
connections if they don't return in 2 milliseconds (maxWait="2")...

HUGE mistake. Changed connection pool parameter to 60 seconds
(maxWait="60000"), and problem has gone.

Just my 2c,

Edson Richter


pgsql-general by date:

Previous
From: David Noel
Date:
Subject: Re: initdb error
Next
From: AI Rumman
Date:
Subject: Re: pg_restore error with out of memory