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
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
