Bug 182115 - SQLite not configure with --enable-threadsafe
Summary: SQLite not configure with --enable-threadsafe
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sqlite3 (Show other bugs)
(Show other bugs)
Version: 4
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-20 17:13 UTC by Derek Atkins
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-14 18:38:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Derek Atkins 2006-02-20 17:13:23 UTC
Description of problem:
I've had trac fail and lock the database, require restarting httpd.  According
to http://projects.edgewall.com/trac/ticket/1661 part of the problem is that
sqlite is not compiled with --enable-threadsafe.  I verified that the FC4 spec
file does indeed fail to configure --enable-threadsafe.

Version-Release number of selected component (if applicable):
[root@cvs ~]# rpm -q sqlite
sqlite-3.1.2-3

How reproducible:
The trac bug I've only seen once, but the lack of threadsafe-mode is 100%
reproducible.

Steps to Reproduce:
1. rpmbuild --rebuild sqlite-3.1.2-3.src.rpm
2. notice that it still doesn't configure with --enable-threadsafe
3. file a bug report to get this fixed.
  
Actual results:
trac database lock due to multithreaded access to sqlite through mod_python

Expected results:
threadsafe access to a sqlite database.

Additional info:

Comment 1 Paul Nasrat 2006-08-14 18:38:42 UTC
Fixed from 3.3.6-1


Note You need to log in before you can comment on or make changes to this bug.