TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30

8,128 views
Skip to first unread message

jo

unread,
Feb 17, 2009, 9:44:03 AM2/17/09
to sa
Hi all,

I wonder what this message mean:

TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30

any ideas?

jo


Marcin Krol

unread,
May 22, 2009, 4:41:24 AM5/22/09
to sqlal...@googlegroups.com
Hello everyone,

After some time of operation (a day or so), from time to time I'm
getting this error:

TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection
timed out, timeout 30

I have to stress that not much activity is taking place on that OS as it
is development installation.

Does anybody know what could be causing this?

Restarting apache or postgres eliminates that problem, but then it
reappears.

I'm getting sick of this. Does anybody know what could be the root
cause? How to fix this?

My app uses mod_python / SQLA 5.3.

The backend is Postgres 8.1 on RH 5.3.

Regards,
mk

Jeff FW

unread,
May 24, 2009, 4:51:18 PM5/24/09
to sqlalchemy
You need to make sure that you are closing your sessions--otherwise,
they keep your connections open, and are never returned to the pool.
Make sure to read up on sessions here:
http://www.sqlalchemy.org/docs/05/session.html

Also, read up on logging:
http://www.sqlalchemy.org/docs/05/dbengine.html#configuring-logging

It's nice to be able to log your pool status at some points, so that
you can see how many connections are open.

-Jeff
Reply all
Reply to author
Forward
0 new messages