Ticket #1661 (closed defect: worksforme)
Database locks after an error involving database with mod_python
| Reported by: | sam | Owned by: | cboos |
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | web frontend/mod_python | Version: | 0.9.4 |
| Severity: | critical | Keywords: | database locked |
| Cc: | sam@…, alexander.neundorf@… |
Description
After a Trac Oops error involving a database operation (such as page edition, generally occuring with concurrent page edition), the database is not closed by mod_python. According to cmlenz, it is the expected behavior because of the connection pool.
But what's not expected is that the DB is then locked for a couple of minutes or until Apache is restarted.
Additionnal information Trac version: trunk/ r1784 Sqlite: 2.8.16-1, from Debian Sid package Python-sqlite: 1.0.1-2, from Debian Sid package
[Sun Jun 12 14:26:06 2005] [notice] Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-15 mod_ssl/2.0.54 OpenSSL/0.9.7g mod_perl/1.999.23 Perl/v5.8.7 configured -- resuming normal operations
Attachments
Change History
Note: See
TracTickets for help on using
tickets.


