#110 After some time, Ipsilon will stop working with remote database
Closed: Fixed None Opened 8 years ago by puiterwijk.

Some time after starting Ipsilon, it will stop responding to requests, because the current database pool has been exhausted and it will not connect until those sessions are cleaned up.

This is shown in the logs by: "[Mon Apr 13 21:07:51.829277 2015] [:error] [pid 7140] TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30"

The reason this happens is because we never exit our database sessions between requests.


Connection pools were added to alleviate the problem and the pgdb test updated to loop over authentications to stress the pool. In the case of sqlite the SingletonThreadPool is used.

master: 800b39d

milestone: 1.0 => 1.0 m4
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @nkinder:
- Issue assigned to puiterwijk
- Issue set to the milestone: 1.0 m4

7 years ago

Login to comment on this ticket.

Metadata