Closed Bug 671098 Opened 13 years ago Closed 13 years ago

Forces a nullpool when sqlite is used

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: tarek, Assigned: tarek)

Details

Attachments

(2 files)

This error :

ProgrammingError: (ProgrammingError) Cannot operate on a closed database. None [{}]

happens on concurrent accesses on sqlite.

we need to make sure storage *and* auth are using NullPool when sqlite is used.
in the default config, and raise a config error if it's the config tries to use pooling
Verified in-house by Owen and myself...
Assignee: nobody → tarek
Attachment #548709 - Flags: review?(rmiller)
Comment on attachment 548709 [details] [diff] [review]
Make sure we use a NullPool when using SQLLite

Review of attachment 548709 [details] [diff] [review]:
-----------------------------------------------------------------

sucks that you have to make some of these changes in 2 places, but other than that this looks fine.
Attachment #548709 - Flags: review?(rmiller) → review+
yes that's because the user/ directory created to refactor things, duplicated the code found in /auth  -- this is one of the reasons I think we should have a another process when refactoring things so we don't dupe code.
done in http://hg.mozilla.org/services/server-core/rev/eabfa9a1744b
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
There's still one spot that needs this
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #549317 - Flags: review?(rmiller)
Attachment #549317 - Flags: review?(rmiller) → review+
http://hg.mozilla.org/services/server-core/rev/df16a6d6d04d
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: