Django and SQL Server 2005 - Zombie status?

Question

I'm using Django 1.2 and django-mssql.

While performing the following

for unicorn in Unicorn.objects.all():
    print unicorn.color

I'm getting the following error at around the 100th iteration:

com_error: (-2147352567, 'Exception occurred.', (0, u'Microsoft SQL Server Nativ e Client 10.0', u'The object is in a zombie state. An object may enter a zombie state when either ITransaction::Commit or ITransaction::Abort is called, or when a storage object was created and not yet released.', None, 0, -2147418113), Non e)

Any idea? This is really bugging me... starting to hate the whole Windows Server world... :(

COM error is not a joke (I'm a former DirectX developer, I see COM errors in my nightmares), and COM error + zombie is a real Resident Evil :-) — Tomasz Zieliński, Nov 16 '10 at 20:32

score 1 · Answer 1 · edited Dec 08 '11 at 00:50

1

I had a similar problem and I resolved it by forcing the full QuerySet to be retrieved before using it in the for loop. So, try this:

for unicorn in list(Unicorn.objects.all()):
    print unicorn.color

edited Dec 08 '11 at 00:50

Brock Adams

90,639
22
233
295

answered Nov 26 '10 at 13:27

Don

16,928
12
63
101

@RadiantHex: Did you find it useful? Have you found the cause of your problem? – Don Dec 06 '10 at 08:48

score 0 · Answer 2 · answered Dec 06 '10 at 10:37

Another way is to set 'can_use_chunked_read = True' in base.DatabaseFeature:

sqlserver_ado/base.py: 16

class DatabaseFeatures(BaseDatabaseFeatures):
    uses_custom_query_class = True
    can_use_chunked_reads = False

I just set it and the error has gone away. Let me know if it solves your problem too.

Django and SQL Server 2005 - Zombie status?

2 Answers2