On 7/19/07, oggie rob <[EMAIL PROTECTED]> wrote: > > Please, if you've seen the same issue or have any helpful ideas to try > to stop the error, let me know.
I think I've seen the same problem (or, at least, an analogous one). Unfortunately, I can't provide much by way of helpful debug or solution - the sysadmin that identified the problem for us isn't around for me to ask him for more details. As I recall, the problem was mod_python. Older versions of mod_python had some sort of issue with caching python instances. As a result, if you deployed two different versions of Django, the version of Django that was provided to a given request was determined by the thread that served the request. If the first request served by a thread used the old version of Django, that was the version that was used for all subsequent requests on that thread, regardless of the version that was required to satisfy the request. I believe we fixed the problem by updating mod_python, but I'm not completely certain on that. I know that this is all vague and ambiguous help - sorry I can't be more specific. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
