On Mar 18, 3:35 pm, Graham Dumpleton <[email protected]> wrote:
> This is not an error from mod_wsgi but from Django and has been > encountered by various people and not just with mod_wsgi. Thanks Graham. I dug through a number of Django references before posting here. I'm on Django 1.0.X so Django ticket #8221 has been fixed and you'll notice that no arguments are being sent to the reverse (as expected) so it is not a regex urlresolver issue. I can view the same page w/ the same content hundreds of times without having an issue, but every day or 2 I get the error. The reason I bring it up here is that the only common thread I can find is the mod_wsgi activity in my Apache error log (pasted in the original email) about it loading the wsgi script at the same time the error occurs. Does mod_wsgi reload the script when 500s are encountered? If not, is it possible for unexpected behavior to occur if we try to access the app during the wsgi script load process? -- Pete --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
