Ticket #3788 (closed defect: duplicate)
Opened 6 years ago
Last modified 6 years ago
Trac connection pool depletion when running multithreaded
| Reported by: | alberto@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | general | Version: | 0.10rc1 |
| Severity: | blocker | Keywords: | |
| Cc: | alberto@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
I have a trac mounted via WSGI in a multithreaded CherryPy? HTTP server and after a few dozen requests the db connections pool seems to get exhausted and Trac freezes up.
Other WSGI apps mounted on the same CP server suffer no lockup while Trac remains locked-up.
I've managed to reproduce both using sqlite and postgres backends.
This message from Trac gets on my server's log:
Exception exceptions.AssertionError: <exceptions.AssertionError instance at 0xa931db4c> in <bound method PooledConnection.__del__ of <trac.db.pool.PooledConnection object at 0xa936b76c>> ignored
Which I believe to be located here
I'm not too familiar with Trac's pool management to submit a patch ATM, sorry.
Attachments
Change History
comment:1 Changed 6 years ago by mgood
- Resolution set to duplicate
- Status changed from new to closed
comment:2 Changed 6 years ago by cboos
Please alberto, can you try to reproduce the issue with latest trunk, to be really sure that it's fixed now?
comment:3 Changed 6 years ago by alberto
Upgraded to trunk and it survived 1000 requests in chunks of 50 concurrent requests so it surely seems fixed. Thanks! :)
Alberto
comment:4 Changed 6 years ago by cboos
Great! Thank you very much for the feedback.
This is a duplicate of #3504 which should be fixed in the trunk now.