#27093: ORM error on apache + wsgi
-------------------------------------+-------------------------------------
     Reporter:  biggosh              |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by biggosh):

 HI,

 thanks. Now I modified the code simply cutting the db update code outside
 the start method of the lxml parser and everything works fine.
 The strange thing is that the error happened only when I copied the code
 to the production system with apache + wsgi. It has never happened during
 development using development server. And second thing: why after a couple
 of page refresh the code works?

 I'll try to reduce the code, but I suspect that there is a problem related
 to multi-process/threading running when deployed on apache and the error
 is due to interaction between "processes"

 Christian

--
Ticket URL: <https://code.djangoproject.com/ticket/27093#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.f67d452956413a00e4cd814e29ab29a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to