Re: Django+ oracle, working with apache(mod_python, wsgi) and in runserver, ora-03114 in fastcgi

On Mar 1, 10:26 am, Ian <ian.g.ke...@gmail.com> wrote:
> It appears that the error is actually from the previous (working)
> request when Django subsequently tries to close the database
> connections and fails, and since the error goes uncaught, it kills the
> server.
>
> It's pretty weird that it would fail in this way.  What happens if you
> explicitly close the database connections at the end of your view?

You'll also need to disable your middleware to test this, in case some
middleware needs the connections active after the view returns.

Also, does this error appear at all in your Apache logs? I wonder if
it was occurring there as well and just going unnoticed.

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.